Ignore:
Timestamp:
06/05/14 12:37:38 (7 years ago)
Author:
julian.reschke@…
Message:

punctuation (#553)

File:
1 edited

Legend:

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

    r2634 r2636  
    492492<t><iref primary="true" item="gateway"/><iref primary="true" item="reverse proxy"/>
    493493<iref primary="true" item="accelerator"/>
    494    A "<x:dfn>gateway</x:dfn>" (a.k.a., "<x:dfn>reverse proxy</x:dfn>") is an
    495    intermediary that acts as an origin server for the outbound connection, but
     494   A "<x:dfn>gateway</x:dfn>" (a.k.a. "<x:dfn>reverse proxy</x:dfn>") is an
     495   intermediary that acts as an origin server for the outbound connection but
    496496   translates received requests and forwards them inbound to another server or
    497497   servers. Gateways are often used to encapsulate legacy or untrusted
     
    643643   element. Furthermore, what is commonly understood to be a reasonable length
    644644   for some protocol elements has changed over the course of the past two
    645    decades of HTTP use, and is expected to continue changing in the future.
     645   decades of HTTP use and is expected to continue changing in the future.
    646646</t>
    647647<t>
     
    11021102   In theory, a client could receive requests and a server could receive
    11031103   responses, distinguishing them by their different start-line formats,
    1104    but in practice servers are implemented to only expect a request
     1104   but, in practice, servers are implemented to only expect a request
    11051105   (a response is interpreted as an unknown or invalid request method)
    11061106   and clients are implemented to only expect a response.
     
    18881888   the value given by Content-Length.  A response that has neither chunked
    18891889   transfer coding nor Content-Length is terminated by closure of the
    1890    connection, and thus is considered complete regardless of the number of
     1890   connection and, thus, is considered complete regardless of the number of
    18911891   message body octets received, provided that the header section was received
    18921892   intact.
     
    27382738   software of each recipient, analogous to the <x:ref>User-Agent</x:ref> and
    27392739   <x:ref>Server</x:ref> header fields. However, all comments in the Via field
    2740    are optional and a recipient &MAY; remove them prior to forwarding the
     2740   are optional, and a recipient &MAY; remove them prior to forwarding the
    27412741   message.
    27422742</t>
     
    31113111   ceiling, but this was found to be impractical for many applications. As a
    31123112   result, this specification does not mandate a particular maximum number of
    3113    connections, but instead encourages clients to be conservative when opening
     3113   connections but, instead, encourages clients to be conservative when opening
    31143114   multiple connections.
    31153115</t>
Note: See TracChangeset for help on using the changeset viewer.