Ignore:
Timestamp:
14/07/12 14:09:09 (9 years ago)
Author:
julian.reschke@…
Message:

header -> header field (#234)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1771 r1772  
    13521352</t>
    13531353<t>
    1354    A client that receives response headers that are longer than it wishes to
    1355    handle can only treat it as a server error.
    1356 </t>
    1357 <t>
    1358    Various ad-hoc limitations on header length are found in practice. It is
    1359    &RECOMMENDED; that all HTTP senders and recipients support messages whose
     1354   A client that receives response header fields that are longer than it wishes
     1355   to handle can only treat it as a server error.
     1356</t>
     1357<t>
     1358   Various ad-hoc limitations on header field length are found in practice. It
     1359   is &RECOMMENDED; that all HTTP senders and recipients support messages whose
    13601360   combined header fields have 4000 or more octets.
    13611361</t>
     
    19961996    recipient could use the message (in a manner acceptable to the server where
    19971997    the field originated) without receiving it. In other words, the server that
    1998     generated the header (often but not always the origin server) is willing to
    1999     accept the possibility that the trailer fields might be silently discarded
    2000     along the path to the client.</t>
     1998    generated the header field (often but not always the origin server) is
     1999    willing to accept the possibility that the trailer fields might be silently
     2000    discarded along the path to the client.</t>
    20012001  </list>
    20022002</t>
     
    49744974   experimental implementations of HTTP/1.0 persistent connections are faulty;
    49754975   for example, if a HTTP/1.0 proxy server doesn't understand
    4976    <x:ref>Connection</x:ref>, it will erroneously forward that header to the
    4977    next inbound server, which would result in a hung connection.
    4978 </t>
    4979 <t>
    4980    One attempted solution was the introduction of a Proxy-Connection header,
    4981    targeted specifically at proxies. In practice, this was also unworkable,
    4982    because proxies are often deployed in multiple layers, bringing about the
    4983    same problem discussed above.
     4976   <x:ref>Connection</x:ref>, it will erroneously forward that header field
     4977   to the next inbound server, which would result in a hung connection.
     4978</t>
     4979<t>
     4980   One attempted solution was the introduction of a Proxy-Connection header
     4981   field, targeted specifically at proxies. In practice, this was also
     4982   unworkable, because proxies are often deployed in multiple layers, bringing
     4983   about the same problem discussed above.
    49844984</t>
    49854985<t>
    49864986   As a result, clients are encouraged not to send the Proxy-Connection header
    4987    in any requests.
     4987   field in any requests.
    49884988</t>
    49894989<t>
     
    49924992   HTTP/1.0 servers, clients using them need will need to monitor the
    49934993   connection for "hung" requests (which indicate that the client ought stop
    4994    sending the header), and this mechanism ought not be used by clients at all
    4995    when a proxy is being used.
     4994   sending the header field), and this mechanism ought not be used by clients
     4995   at all when a proxy is being used.
    49964996</t>
    49974997</section>
     
    54315431  <list style="symbols">
    54325432    <t>
    5433       Reference RFC 3984, and update header field registrations for headers defined
    5434       in this document.
     5433      Reference RFC 3984, and update header field registrations for header
     5434      fields defined in this document.
    54355435    </t>
    54365436  </list>
     
    54725472    <t>
    54735473      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/129"/>:
    5474       "List-type headers vs Set-Cookie"
     5474      "List-type header fields vs Set-Cookie"
    54755475    </t>
    54765476  </list>
     
    56345634    <t>
    56355635      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/93"/>:
    5636       "Repeating single-value headers"
     5636      "Repeating single-value header fields"
    56375637    </t>
    56385638    <t>
     
    57015701    <t>
    57025702      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/200"/>:
    5703       "use of term "word" when talking about header structure"
     5703      "use of term "word" when talking about header field structure"
    57045704    </t>
    57055705  </list>
     
    57335733    <t>
    57345734      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/200"/>:
    5735       "use of term "word" when talking about header structure"
     5735      "use of term "word" when talking about header field structure"
    57365736    </t>
    57375737  </list>
     
    57625762    <t>
    57635763      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/95"/>:
    5764       "Handling multiple Content-Length headers"
     5764      "Handling multiple Content-Length header fields"
    57655765    </t>
    57665766    <t>
     
    58125812    <t>
    58135813      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/95"/>:
    5814       "Handling multiple Content-Length headers"
     5814      "Handling multiple Content-Length header fields"
    58155815    </t>
    58165816  </list>
     
    58365836    <t>
    58375837      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/224"/>:
    5838       "Header Classification"
     5838      "Header Field Classification"
    58395839    </t>
    58405840    <t>
     
    58685868    <t>
    58695869      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/95"/>:
    5870       "Handling multiple Content-Length headers"
     5870      "Handling multiple Content-Length header fields"
    58715871    </t>
    58725872    <t>
     
    59405940    <t>
    59415941      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/215"/>:
    5942       "Explain header registration"
     5942      "Explain header field registration"
    59435943    </t>
    59445944    <t>
Note: See TracChangeset for help on using the changeset viewer.