Ignore:
Timestamp:
19/05/14 13:38:02 (6 years ago)
Author:
julian.reschke@…
Message:

updated AUTH48 version of RFC7231 (#553)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/auth48/rfc7231.abdiff.txt

    r2680 r2682  
    77 Obsoletes: 2616 (if approved)                            J. Reschke, Ed.
    88 Updates: 2817 (if approved)                                   greenbytes
    9  Intended status: Standards Track                            May 16, 2014
    10  Expires: November 17, 2014
     9 Intended status: Standards Track                            May 19, 2014
     10 Expires: November 20, 2014
    1111
    1212NEW:
     
    9191OLD:
    9292
    93     This Internet-Draft will expire on November 17, 2014.
     93    This Internet-Draft will expire on November 20, 2014.
    9494
    9595NEW:
     
    299299      6.3.  Successful 2xx . . . . . . . . . . . . . . . . . . . . . . 51
    300300        6.3.1.  200 OK . . . . . . . . . . . . . . . . . . . . . . . . 51
    301         6.3.2.  201 Created  . . . . . . . . . . . . . . . . . . . . . 52
     301        6.3.2.  201 Created  . . . . . . . . . . . . . . . . . . . . . 51
    302302        6.3.3.  202 Accepted . . . . . . . . . . . . . . . . . . . . . 52
    303303        6.3.4.  203 Non-Authoritative Information  . . . . . . . . . . 52
     
    429429    identifier.  A sender SHOULD NOT generate information in product-
    430430    version that is not a version identifier (i.e., successive versions
    431     of the same product name ought only to differ in the product-version
     431    of the same product name ought to differ only in the product-version
    432432    portion of the product identifier).
    433 
    434 
    435 Section 6.2., paragraph 1:
    436 OLD:
    437 
    438     The 1xx (Informational) class of status code indicates an interim
    439     response for communicating connection status or request progress
    440     prior to completing the requested action and sending a final
    441     response. 1xx responses are terminated by the first empty line after
    442     the status-line (the empty line signaling the end of the header
    443     section).  Since HTTP/1.0 did not define any 1xx status codes, a
    444     server MUST NOT send a 1xx response to an HTTP/1.0 client.
    445 
    446 NEW:
    447 
    448     The 1xx (Informational) class of status code indicates an interim
    449     response for communicating connection status or request progress
    450     prior to completing the requested action and sending a final
    451     response.  All 1xx responses consist of only the status-line and
    452     optional header fields and, thus, are terminated by the empty line at
    453     the end of the header section.  Since HTTP/1.0 did not define any 1xx
    454     status codes, a server MUST NOT send a 1xx response to an HTTP/1.0
    455     client.
    456433
    457434
     
    468445      ; fixed length/zone/capitalization subset of the format
    469446      ; defined in Section 3.3 of [RFC5322]
    470 
    471 
    472 Section 9.1., paragraph 1:
    473 OLD:
    474 
    475     Origin servers frequently make use of their local file system to
    476     manage the mapping from effective request URI to resource
    477     representations.  Most file systems are not designed to protect
    478     against malicious file or path names.  Therefore, an origin server
    479     needs to avoid accessing names that have a special significance to
    480     the system when mapping the request target to files, folders, or
    481     directories.
    482 
    483 NEW:
    484 
    485     Origin servers frequently make use of their local file system to
    486     manage the mapping from effective request URI to resource
    487     representations.  Implementers need to be aware that most file
    488     systems are not designed to protect against malicious file or path
    489     names and, thus, depend on the origin server to avoid mapping to file
    490     names, folders, or directories that have special significance to the
    491     system.
    492447
    493448
     
    903858
    904859
    905 Section 1.2, paragraph 34:
    906 OLD:
    907 
    908     2
    909        200 OK (status code)  51
    910        201 Created (status code)  51
    911        202 Accepted (status code)  52
    912        203 Non-Authoritative Information (status code)  52
    913        204 No Content (status code)  53
    914        205 Reset Content (status code)  53
    915 
    916 NEW:
    917 
    918     2
    919        200 OK (status code)  51
    920        201 Created (status code)  52
    921        202 Accepted (status code)  52
    922        203 Non-Authoritative Information (status code)  52
    923        204 No Content (status code)  53
    924        205 Reset Content (status code)  53
    925 
    926 
    927860Section 1.2, paragraph 47:
    928861OLD:
Note: See TracChangeset for help on using the changeset viewer.