[OPC] Discrepancy 1: Two charcters { (U+005b) and } (U+005d)

MURATA Makoto eb2m-mrt at asahi-net.or.jp
Tue Apr 7 12:01:56 CEST 2015


Folks,

I am going to post a sequence of emails for describing
syntactical discrepancies among OPC, legacy HTTP 1.1,
and revised HTTP 1.1.

This e-mail is about two charcters { (U+005b) and } (U+005d).  Are
they allowed as part of a token (and thus type/subtype/parameter
name)?

OPC as of now:  Disallowed

  [\p{IsBasicLatin}-[\p{Cc}\(\)<>@,;:\\"/\[\]\?=\{\}\s\t]]

Legacy HTTP 1.1: Allowed

  (tspecials are excluded (a negative list) )

     tspecials :=  "(" / ")" / "<" / ">" / "@" /
                   "," / ";" / ":" / "\" / <">
                   "/" / "[" / "]" / "?" / "="
                   ; Must be in quoted-string,
                   ; to use within parameter values" /

Revsied HTTP 1.1: Disallowed

  (tchar is a positive list)

     tchar          = "!" / "#" / "$" / "%" / "&" / "'" / "*"
                    / "+" / "-" / "." / "^" / "_" / "`" / "|" / "~"
                    / DIGIT / ALPHA
                    ; any VCHAR, except delimiters


Regards,
Makoto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20150407/594645de/attachment.html>


More information about the sc34wg4 mailing list