search

quicwg / base-drafts

Internet-Drafts that make up the base QUIC specification
https://quicwg.org
1.62k stars 204 forks source link

Auth48: References to ASCII characters #4952

Closed MikeBishop closed 2 years ago

MikeBishop commented 2 years ago

The RFC Editor asks:

Please review the way characters and ASCII equivalents are displayed with regard to quotation and whether the ASCII value is listed etc. and let us know if/how to update.

  • ':' character (ASCII 0x3a)
  • "?" character
  • the value '*'
  • 0x3b, 0x20 (the ASCII string "; ")
  • carriage return (CR, ASCII 0xd)
  • line feed (LF, ASCII 0xa)
  • zero character (NUL, ASCII 0x0
MikeBishop commented 2 years ago

Along the way, there are two equivalent statements that need to be deduplicated that this change touches:

Contains the path and query parts of the target URI (the "path-absolute" production and optionally a '?' character followed by the "query" production; see Sections 3.3 and 3.4 of [URI]. *A request in asterisk form includes the value '' for the ":path" pseudo-header field.**

This pseudo-header field MUST NOT be empty for "http" or "https" URIs; "http" or "https" URIs that do not contain a path component MUST include a value of '/'. *The exception to this rule is an OPTIONS request for an "http" or "https" URI that does not include a path component; these MUST include a ":path" pseudo-header field with a value of ''; see Section 7.1 of [HTTP].**

I would suggest collapsing these two into the first statement, but using OPTIONS as an example and keeping the reference into http-core.

Or perhaps that should be a question -- is there a difference between asterisk-form and OPTIONS-without-path?

MikeBishop commented 2 years ago

Resolved in #4960.