- From: Kari hurtta <hurtta-ietf@elmme-mailer.org>
- Date: Wed, 3 Aug 2016 12:37:51 +0300 (EEST)
- To: Willy Tarreau <w@1wt.eu>
- CC: Kari hurtta <hurtta-ietf@elmme-mailer.org>, HTTP working group mailing list <ietf-http-wg@w3.org>, Mark Nottingham <mnot@mnot.net>, Poul-Henning Kamp <phk@phk.freebsd.dk>
Willy Tarreau <w@1wt.eu>: (Wed Aug 3 09:46:33 2016) > On Wed, Aug 03, 2016 at 09:37:30AM +0300, Kari hurtta wrote: > > | 2) Regardless of #1, using < as your indicator character is going to collide with the existing syntax of the > > | Link header. > > > > Or perhaps use ':' as indicator? Causes double '::' on HTTP/1 > > > > Date::1470205476 > > > > Is this viable ? > > It could but strictly speaking it will not be "::", it would just be ":" > to start the value, because your field above parses as ":1470205476" for > the value and will be rewritten like this along the path by many > implementations : > > Date: :1470205476 Yes, that is true. Another possibility is use indicator from ascii control block. For example byte 01. Does not collide with existing use. That is Date:1470205476 on HTTP/1 (but probaly not visible; first character after ':' is byte 01 (ctrl-A)). ( I think that someone suggested that already. ) ( byte 01 seems to be valid TEXT on ABNF ? ) > Willy / Kari Hurtta
Received on Wednesday, 3 August 2016 09:41:21 UTC