Changes between Version 10 and Version 15 of Ticket #502


Ignore:
Timestamp:
04/11/13 22:42:38 (9 years ago)
Author:
fielding@…
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #502

    • Property Severity changed from In WG Last Call to In IETF LC

  • Ticket #502 – Description

    v10 v15  
    1717The client would have to track the version supported by the server once it knows that information. A server can be one or more HTTP implementations. In practice these implementations will likely support HTTP 1.1. I'll list the "and whose major version is no higher than the highest version supported ..." as an issue. Is the intent to ensure that the client can work with HTTP 2.0?
    1818
     19''WONTFIX''
     20
    1921----
    2022
    21   "A server MAY send a 505 (HTTP Version Not Supported) response if it cannot send a response using the major version used in the client's request."
     23~~  "A server MAY send a 505 (HTTP Version Not Supported) response if it cannot send a response using the major version used in the client's request."~~
    2224
    23 Why is this a RFC 2119 "may"?
     25~~Why is this a RFC 2119 "may"?~~
    2426
    2527----
    … …  
    2931  "An intermediary MUST NOT forward a message to itself unless it is protected from an infinite request loop.  In general, an intermediary ought to recognize its own server names, including any aliases, local variations, or literal IP addresses, and respond to such requests directly."
    3032
    31 I don't understand why an intermediary would forward a message to itself. Please note that I do not consider this prohibition as an issue.
     33I don't understand why an intermediary would forward a message to itself.
     34Please note that I do not consider this prohibition as an issue.
     35
     36''Because they do. WONTFIX''
    3237
    3338----