Changes between Version 3 and Version 4 of Ticket #522


Ignore:
Timestamp:
08/12/13 14:13:08 (6 years ago)
Author:
julian.reschke@…
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #522 – Description

    v3 v4  
    1313----
    1414
    15 In section 2.1, in third to last paragraph, why is ought used here
    16 instead of a keyword?  This is a point that could help with
    17 interoperability, so I think a keyword is important.  Unless there is
    18 another error message, one should be provided when the role access
    19 requirements are not met.  Users would expect this functionality.
     15~~~In section 2.1, in third to last paragraph, why is ought used here instead of a keyword?  This is a point that could help with interoperability, so I think a keyword is important.  Unless there is another error message, one should be provided when the role access requirements are not met.  Users would expect this functionality.~~ - see http://lists.w3.org/Archives/Public/ietf-http-wg/2013OctDec/1147.html
    2016
    2117----
    2218Nits/editorial comments:
    2319----
    24 Section 3.2.1 - please fix the run-on sentence, the first one as it is
    25 difficult to read.  Suggestion: From:
     20~~Section 3.2.1 - please fix the run-on sentence, the first one as it is
     21difficult to read.  Suggestion: From:~~
    2622
    27     If a server receives a request for an access-protected object, and an acceptable Authorization header is not sent, the server responds with a "401 Unauthorized" status code, and a WWW-Authenticate header as per the framework defined above, which for the digest scheme is utilized as follows:
     23    ~~If a server receives a request for an access-protected object, and an acceptable Authorization header is not sent, the server responds with a "401 Unauthorized" status code, and a WWW-Authenticate header as per the framework defined above, which for the digest scheme is utilized as follows:~~
    2824
    29 To:
     25~~To:~~
    3026
    31     If a server receives a request for an access-protected object and an acceptable Authorization header is not sent.  The server responds with a "401 Unauthorized" status code and a WWW-Authenticate header as per the framework defined above.  For the digest scheme, this is utilized as follows:
     27    ~~If a server receives a request for an access-protected object and an acceptable Authorization header is not sent.  The server responds with a "401 Unauthorized" status code and a WWW-Authenticate header as per the framework defined above.  For the digest scheme, this is utilized as follows:~~ -- see http://lists.w3.org/Archives/Public/ietf-http-wg/2013OctDec/1147.html
    3228
    3329----