Ignore:
Timestamp:
16/05/14 06:54:01 (6 years ago)
Author:
julian.reschke@…
Message:

Apply Roy Fielding's feedback to P2 (#553)

File:
1 edited

Legend:

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

    r2678 r2679  
    77 Obsoletes: 2616 (if approved)                            J. Reschke, Ed.
    88 Updates: 2817 (if approved)                                   greenbytes
    9  Intended status: Standards Track                            May 15, 2014
    10  Expires: November 16, 2014
     9 Intended status: Standards Track                            May 16, 2014
     10 Expires: November 17, 2014
    1111
    1212NEW:
     
    9191OLD:
    9292
    93     This Internet-Draft will expire on November 16, 2014.
     93    This Internet-Draft will expire on November 17, 2014.
    9494
    9595NEW:
     
    157157      6.3.  Successful 2xx . . . . . . . . . . . . . . . . . . . . . . 51
    158158        6.3.1.  200 OK . . . . . . . . . . . . . . . . . . . . . . . . 51
    159         6.3.2.  201 Created  . . . . . . . . . . . . . . . . . . . . . 52
     159        6.3.2.  201 Created  . . . . . . . . . . . . . . . . . . . . . 51
    160160        6.3.3.  202 Accepted . . . . . . . . . . . . . . . . . . . . . 52
    161161        6.3.4.  203 Non-Authoritative Information  . . . . . . . . . . 52
     
    411411
    412412
     413Section 5.5.3., paragraph 5:
     414OLD:
     415
     416    A sender SHOULD limit generated product identifiers to what is
     417    necessary to identify the product; a sender MUST NOT generate
     418    advertising or other nonessential information within the product
     419    identifier.  A sender SHOULD NOT generate information in product-
     420    version that is not a version identifier (i.e., successive versions
     421    of the same product name only to differ only in the product-version
     422    portion of the product identifier).
     423
     424NEW:
     425
     426    A sender SHOULD limit generated product identifiers to what is
     427    necessary to identify the product; a sender MUST NOT generate
     428    advertising or other nonessential information within the product
     429    identifier.  A sender SHOULD NOT generate information in product-
     430    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
     432    portion of the product identifier).
     433
     434
    413435Section 6.1., paragraph 3:
    414436OLD:
     
    509531
    510532
     533Section 6.2., paragraph 1:
     534OLD:
     535
     536    The 1xx (Informational) class of status code indicates an interim
     537    response for communicating connection status or request progress
     538    prior to completing the requested action and sending a final
     539    response. 1xx responses are terminated by the first empty line after
     540    the status-line (the empty line signaling the end of the header
     541    section).  Since HTTP/1.0 did not define any 1xx status codes, a
     542    server MUST NOT send a 1xx response to an HTTP/1.0 client.
     543
     544NEW:
     545
     546    The 1xx (Informational) class of status code indicates an interim
     547    response for communicating connection status or request progress
     548    prior to completing the requested action and sending a final
     549    response.  All 1xx responses consist of only the status-line and
     550    optional header fields and, thus, are terminated by the empty line at
     551    the end of the header section.  Since HTTP/1.0 did not define any 1xx
     552    status codes, a server MUST NOT send a 1xx response to an HTTP/1.0
     553    client.
     554
     555
    511556Section 7.1.1.1., paragraph 10:
    512557OLD:
     
    521566      ; fixed length/zone/capitalization subset of the format
    522567      ; defined in Section 3.3 of [RFC5322]
     568
     569
     570Section 9.1., paragraph 1:
     571OLD:
     572
     573    Origin servers frequently make use of their local file system to
     574    manage the mapping from effective request URI to resource
     575    representations.  Most file systems are not designed to protect
     576    against malicious file or path names.  Therefore, an origin server
     577    needs to avoid accessing names that have a special significance to
     578    the system when mapping the request target to files, folders, or
     579    directories.
     580
     581NEW:
     582
     583    Origin servers frequently make use of their local file system to
     584    manage the mapping from effective request URI to resource
     585    representations.  Implementers need to be aware that most file
     586    systems are not designed to protect against malicious file or path
     587    names and, thus, depend on the origin server to avoid mapping to file
     588    names, folders, or directories that have special significance to the
     589    system.
    523590
    524591
     
    9341001
    9351002
     1003Section 1.2, paragraph 34:
     1004OLD:
     1005
     1006    2
     1007       200 OK (status code)  51
     1008       201 Created (status code)  51
     1009       202 Accepted (status code)  52
     1010       203 Non-Authoritative Information (status code)  52
     1011       204 No Content (status code)  53
     1012       205 Reset Content (status code)  53
     1013
     1014NEW:
     1015
     1016    2
     1017       200 OK (status code)  51
     1018       201 Created (status code)  52
     1019       202 Accepted (status code)  52
     1020       203 Non-Authoritative Information (status code)  52
     1021       204 No Content (status code)  53
     1022       205 Reset Content (status code)  53
     1023
     1024
    9361025Section 1.2, paragraph 47:
    9371026OLD:
Note: See TracChangeset for help on using the changeset viewer.