Ignore:
Timestamp:
21/02/13 11:02:59 (7 years ago)
Author:
julian.reschke@…
Message:

Mention in header field considerations that leading/trailing WS is lossy (see #434)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2184 r2186  
    3131  <!ENTITY whitespace                 "<xref target='Part1' x:rel='#whitespace' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3232  <!ENTITY field-components           "<xref target='Part1' x:rel='#field.components' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     33  <!ENTITY field-parsing              "<xref target='Part1' x:rel='#field.parsing' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3334  <!ENTITY uri                        "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3435  <!ENTITY effective-request-uri      "<xref target='Part1' x:rel='#effective.request.uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    45554556</t>
    45564557<t>
     4558   Leading and trailing whitespace in raw field values is removed upon field
     4559   parsing (&field-parsing;). Field definitions where leading or trailing
     4560   whitespace in values is significant will have to use a container syntax such
     4561   as quoted-string.
     4562</t>
     4563<t>
    45574564   Because commas (",") are used as a generic delimiter between field-values,
    45584565   they need to be treated with care if they are allowed in the field-value.
     
    62266233      "Accept-Language ordering for identical qvalues"
    62276234    </t>
     6235    <t>
     6236      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/434"/>:
     6237      "mention in header field considerations that leading/trailing WS is lossy"
     6238    </t>
    62286239  </list>
    62296240</t>
Note: See TracChangeset for help on using the changeset viewer.