Changeset 1266


Ignore:
Timestamp:
Apr 7, 2011, 2:16:43 AM (9 years ago)
Author:
julian.reschke@…
Message:

src reformat

File:
1 edited

Legend:

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

    r1261 r1266  
    881881   completed without transferring data already held by the client.
    882882</t>
    883 <t>Bodies on GET requests have no defined semantics. Note that sending a body
    884   on a GET request might cause some existing implementations to reject the
    885   request.
     883<t>
     884   Bodies on GET requests have no defined semantics. Note that sending a body
     885   on a GET request might cause some existing implementations to reject the
     886   request.
    886887</t>
    887888<t>
     
    919920   stale.
    920921</t>
    921 <t>Bodies on HEAD requests have no defined semantics. Note that sending a body
    922   on a HEAD request might cause some existing implementations to reject the
    923   request.
     922<t>
     923   Bodies on HEAD requests have no defined semantics. Note that sending a body
     924   on a HEAD request might cause some existing implementations to reject the
     925   request.
    924926</t>
    925927</section>
     
    11231125   but the response does not include a representation.
    11241126</t>
    1125 <t>Bodies on DELETE requests have no defined semantics. Note that sending a body
    1126   on a DELETE request might cause some existing implementations to reject the
    1127   request.
     1127<t>
     1128   Bodies on DELETE requests have no defined semantics. Note that sending a body
     1129   on a DELETE request might cause some existing implementations to reject the
     1130   request.
    11281131</t>
    11291132<t>
     
    12011204
    12021205</artwork></figure>
    1203 <t>Bodies on CONNECT requests have no defined semantics. Note that sending a body
    1204   on a CONNECT request might cause some existing implementations to reject the
    1205   request.
     1206<t>
     1207   Bodies on CONNECT requests have no defined semantics. Note that sending a body
     1208   on a CONNECT request might cause some existing implementations to reject the
     1209   request.
    12061210</t>
    12071211<t>
Note: See TracChangeset for help on using the changeset viewer.