16/05/14 06:54:01 (7 years ago)

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

1 edited


  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2667 r2679  
    25802580   A sender &SHOULD-NOT; generate information in <x:ref>product-version</x:ref>
    25812581   that is not a version identifier (i.e., successive versions of the same
    2582    product name ought only to differ in the product-version portion of the
     2582   product name only to differ only in the product-version portion of the
    25832583   product identifier).
    27382738   interim response for communicating connection status or request progress
    27392739   prior to completing the requested action and sending a final response.
    2740    All 1xx responses consist of only the status-line and optional header
    2741    fields and, thus, are terminated by the empty line at the end of the header
    2742    section.
     2740   1xx responses are terminated by the first empty line after the
     2741   status-line (the empty line signaling the end of the header section).
    27432742   Since HTTP/1.0 did not define any 1xx status codes, a server &MUST-NOT; send
    27442743   a 1xx response to an HTTP/1.0 client.
    49384937   Origin servers frequently make use of their local file system to manage the
    49394938   mapping from effective request URI to resource representations.
    4940    Implementers need to be aware that most file systems are not designed to
    4941    protect against malicious file or path names and, thus, depend on the
    4942    origin server to avoid mapping to file names, folders, or directories that
    4943    have special significance to the system.
     4939   Most file systems are not designed to protect against malicious file
     4940   or path names. Therefore, an origin server needs to avoid accessing
     4941   names that have a special significance to the system when mapping the
     4942   request target to files, folders, or directories.
Note: See TracChangeset for help on using the changeset viewer.