Ignore:
Timestamp:
Jul 24, 2010, 2:23:44 AM (9 years ago)
Author:
julian.reschke@…
Message:

Remove "Changes from RFC 2068" sections (see #220)

File:
1 edited

Legend:

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

    r910 r911  
    32683268</references>
    32693269
    3270 <section title="Compatibility with Previous Versions" anchor="compatibility">
    3271 <section title="Changes from RFC 2068" anchor="changes.from.rfc.2068">
    3272 <t>
    3273    Clarified which error code should be used for inbound server failures
    3274    (e.g., DNS failures). (<xref target="status.504"/>).
    3275 </t>
    3276 <t>
    3277    201 (Created) had a race that required an ETag be sent when a resource is
    3278    first created. (<xref target="status.201"/>).
    3279 </t>
    3280 <t>
    3281    303 (See Also) and 307 (Temporary Redirect) added to address user agent
    3282    failure to implement status code 302 properly.
    3283    (Section <xref target="status.303" format="counter"/> and <xref target="status.307" format="counter"/>)
    3284 </t>
    3285 <t>
    3286    Rewrite of message transmission requirements to make it much harder
    3287    for implementors to get it wrong, as the consequences of errors here
    3288    can have significant impact on the Internet, and to deal with the
    3289    following problems:
    3290   <list style="numbers">
    3291       <t>Changing "HTTP/1.1 or later" to "HTTP/1.1", in contexts where
    3292          this was incorrectly placing a requirement on the behavior of
    3293          an implementation of a future version of HTTP/1.x</t>
    3294 
    3295       <t>Made it clear that user-agents should retry requests, not
    3296          "clients" in general.</t>
    3297 
    3298       <t>Converted requirements for clients to ignore unexpected 100
    3299          (Continue) responses, and for proxies to forward 100 responses,
    3300          into a general requirement for 1xx responses.</t>
    3301 
    3302       <t>Modified some TCP-specific language, to make it clearer that
    3303          non-TCP transports are possible for HTTP.</t>
    3304 
    3305       <t>Require that the origin server &MUST-NOT; wait for the request
    3306          body before it sends a required 100 (Continue) response.</t>
    3307 
    3308       <t>Allow, rather than require, a server to omit 100 (Continue) if
    3309          it has already seen some of the request body.</t>
    3310 
    3311       <t>Allow servers to defend against denial-of-service attacks and
    3312          broken clients.</t>
    3313   </list>
    3314 </t>
    3315 <t>
    3316    This change adds the Expect header and 417 status code.
    3317 </t>
    3318 <t>
    3319    Clean up confusion between 403 and 404 responses. (Section <xref target="status.403" format="counter"/>,
    3320    <xref target="status.404" format="counter"/>, and <xref target="status.410" format="counter"/>)
    3321 </t>
    3322 <t>
    3323    The PATCH<iref item="PATCH method" primary="true"/><iref item="Methods" subitem="PATCH" primary="true"/>, LINK<iref item="LINK method" primary="true"/><iref item="Methods" subitem="LINK" primary="true"/>, UNLINK<iref item="UNLINK method" primary="true"/><iref item="Methods" subitem="UNLINK" primary="true"/> methods were defined but not commonly
    3324    implemented in previous versions of this specification. See <xref target="RFC2068" x:fmt="of" x:sec="19.6.1"/>.
    3325 </t>
    3326 </section>
    3327 
    33283270<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
    33293271<t>
     
    33763318  (<xref target="header.server"/>)
    33773319</t>
    3378 </section>
    3379 
    33803320</section>
    33813321
     
    38593799      "Status codes and caching"
    38603800    </t>
     3801    <t>
     3802      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/220"/>:
     3803      "consider removing the 'changes from 2068' sections"
     3804    </t>
    38613805  </list>
    38623806</t>
Note: See TracChangeset for help on using the changeset viewer.