W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2013

Proposed text for "Routing Data's relationship to headers" (Issue 23)

From: Alexey Melnikov <alexey.melnikov@isode.com>
Date: Wed, 13 Mar 2013 18:14:35 +0000
Message-ID: <5140C20A.8050402@isode.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
The ticket reads:

> Right now, routing data (in particular, :scheme, :host and :path) 
> appear as headers along with the rest. This means that the recipient 
> needs to parse through the header collection to find them -- 
> potentially at the end. Different ways of addressing this have been 
> proposed; e.g., requiring them to be at the top of the header block, 
> or serialising them in different fields.
>

I am proposing to add the following text to both "Request" and 
"Response" subsections of the "HTTP Request/Response" section:

     All header field names starting with ":" (whether defined in this 
document or future
     extensions to this document) MUST appear before any other header 
fields.

Additionally, the following text should be moved from the Security 
Considerations section into the "HTTP Request/Response" section:

         <section title="HTTP Header Fields and HTTP/2.0 Headers">
           <t>
             At the application level, HTTP uses name-value pairs in its 
header fields.  Because HTTP/2.0
             merges the existing HTTP header fields with HTTP/2.0 
headers, there is a possibility that some
             HTTP applications already use a particular header field 
name.  To avoid any conflicts, all
             headers introduced for layering HTTP over HTTP/2.0 are 
prefixed with ":".  ":" is not a
             valid sequence in HTTP/1.* header field naming, preventing 
any possible conflict.
           </t>
         </section>

Does this look reasonable to people?

Thanks,
Alexey
Received on Wednesday, 13 March 2013 18:14:58 GMT

This archive was generated by hypermail 2.3.1 : Wednesday, 13 March 2013 18:15:00 GMT