* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #332: 332.diff

File 332.diff, 2.4 KB (added by julian.reschke@gmx.de, 3 years ago)

proposed change for p2

  • p2-semantics.xml

     
    17691769</t> 
    17701770<t> 
    17711771   The new permanent URI &SHOULD; be given by the Location field in the 
    1772    response. Unless the request method was HEAD, the representation of the 
    1773    response &SHOULD; contain a short hypertext note with a hyperlink to 
    1774    the new URI(s). 
     1772   response. A response payload can contain a short hypertext note with a 
     1773   hyperlink to the new URI(s). 
    17751774</t> 
    17761775<t> 
    17771776   If the 301 status code is received in response to a request method 
     
    18011800</t> 
    18021801<t> 
    18031802   The temporary URI &SHOULD; be given by the Location field in the 
    1804    response. Unless the request method was HEAD, the representation of the 
    1805    response &SHOULD; contain a short hypertext note with a hyperlink to 
    1806    the new URI(s). 
     1803   response. A response payload can contain a short hypertext note with a 
     1804   hyperlink to the new URI(s). 
    18071805</t> 
    18081806<t> 
    18091807   If the 302 status code is received in response to a request method 
     
    19051903</t> 
    19061904<t> 
    19071905   The temporary URI &SHOULD; be given by the Location field in the 
    1908    response. Unless the request method was HEAD, the representation of the 
    1909    response &SHOULD; contain a short hypertext note with a hyperlink to 
    1910    the new URI(s). 
     1906   response. A response payload can contain a short hypertext note with a 
     1907   hyperlink to the new URI(s). 
    19111908</t> 
    19121909<t> 
    19131910   If the 307 status code is received in response to a request method 
     
    39873984  (<xref target="status.203"/>) 
    39883985</t> 
    39893986<t> 
     3987  Removed the normative requirements on response payloads for status codes 
     3988  301, 302, and 307. 
     3989  (<xref target="status.3xx"/>) 
     3990</t> 
     3991<t> 
    39903992  Failed to consider that there are many other request methods that are safe 
    39913993  to automatically redirect, and further that the user agent is able to make 
    39923994  that determination based on the request method semantics. 
     
    47574759  Closed issues: 
    47584760  <list style="symbols">  
    47594761    <t> 
     4762      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/332"/>: 
     4763      "relax requirements on hypertext in 3/4/5xx error responses" 
     4764    </t> 
     4765    <t> 
    47604766      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/333"/>: 
    47614767      "example for 426 response should have a payload" 
    47624768    </t>