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

Ticket #285: 285.diff

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

proposed patch for p2 and p3

  • p2-semantics.xml

     
    7373  <!ENTITY status-407                 "<xref target='Part7' x:rel='#status.407' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 
    7474  <!ENTITY status-412                 "<xref target='Part4' x:rel='#status.412' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 
    7575  <!ENTITY status-416                 "<xref target='Part5' x:rel='#status.416' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 
     76  <!ENTITY p3-header-fields           "<xref target='Part3' x:rel='#header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 
    7677  <!ENTITY p4-status-codes            "<xref target='Part4' x:rel='#status.code.definitions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 
    7778  <!ENTITY p5-status-codes            "<xref target='Part5' x:rel='#status.code.definitions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 
    7879  <!ENTITY p7-status-codes            "<xref target='Part7' x:rel='#status.code.definitions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 
     
    18161817<t> 
    18171818   The resource identified by the request is only capable of generating 
    18181819   response representations which have content characteristics not acceptable 
    1819    according to the accept header fields sent in the request. 
     1820   according to the Accept and Accept-* header fields sent in the request 
     1821   (see &p3-header-fields;). 
    18201822</t> 
    18211823<t> 
    18221824   Unless it was a HEAD request, the response &SHOULD; include a representation 
     
    41574159 
    41584160<section title="Since draft-ietf-httpbis-p2-semantics-15" anchor="changes.since.15"> 
    41594161<t> 
    4160   None yet. 
     4162  Closed issues: 
     4163  <list style="symbols">  
     4164    <t> 
     4165      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/285"/>: 
     4166      "Strength of requirements on Accept re: 406" 
     4167    </t> 
     4168  </list> 
    41614169</t> 
    41624170</section> 
    41634171</section> 
  • p3-payload.xml

     
    844844  </list> 
    845845</t> 
    846846<t> 
     847   Server-driven negotiation allows the user agent to specify its preferences, 
     848   but it cannot expect responses to always honour them. For example, the origin 
     849   server might not implement server-driven negotiation, or it might decide that 
     850   sending a response that doesn't conform to them is better than sending a 406 
     851   (Not Acceptable) response. 
     852</t> 
     853<t> 
     854   Many of the mechanisms for expressing preferences use quality values to 
     855   declare relative preference. See &qvalue; for more information.  
     856</t> 
     857<t> 
    847858   HTTP/1.1 includes the following header fields for enabling 
    848859   server-driven negotiation through description of user agent 
    849860   capabilities and user preferences: Accept (<xref target="header.accept"/>), Accept-Charset 
     
    972983</t> 
    973984<t> 
    974985   If no Accept header field is present, then it is assumed that the 
    975    client accepts all media types. If an Accept header field is present, 
    976    and if the server cannot send a response which is acceptable 
    977    according to the combined Accept field value, then the server &SHOULD; 
    978    send a 406 (Not Acceptable) response. 
     986   client accepts all media types. If an Accept header field is present in a 
     987   request, but the server cannot send a response which is acceptable, then 
     988   the server can either send a response in another format, or a 406 (Not 
     989   Acceptable) response.  
    979990</t> 
    980991<t> 
    981992   A more elaborate example is 
     
    10691080</t> 
    10701081<t> 
    10711082   If no Accept-Charset header field is present, the default is that any 
    1072    character encoding is acceptable. If an Accept-Charset header field is present, 
    1073    and if the server cannot send a response which is acceptable 
    1074    according to the Accept-Charset header field, then the server &SHOULD; send 
    1075    an error response with the 406 (Not Acceptable) status code, though 
    1076    the sending of an unacceptable response is also allowed. 
     1083   character encoding is acceptable. If an Accept-Charset header field is 
     1084   present in a request, but the server cannot send a response which is 
     1085   acceptable, then the server can either use another character encoding, or 
     1086   send a 406 (Not Acceptable) response. 
    10771087</t> 
    10781088</section> 
    10791089 
     
    11301140  </list> 
    11311141</t> 
    11321142<t> 
    1133    If an Accept-Encoding field is present in a request, and if the 
    1134    server cannot send a response which is acceptable according to the 
    1135    Accept-Encoding header field, then the server &SHOULD; send an error response 
    1136    with the 406 (Not Acceptable) status code. 
     1143   If an Accept-Encoding field is present in a request, but the server cannot 
     1144   send a response which is acceptable, then the server &SHOULD; send a 
     1145   response without any encoding (i.e., the "identity" encoding). 
    11371146</t> 
    11381147<t> 
    11391148   If no Accept-Encoding field is present in a request, the server &MAY; 
     
    30103019 
    30113020<section title="Since draft-ietf-httpbis-p3-payload-15" anchor="changes.since.15"> 
    30123021<t> 
    3013   None yet. 
     3022  Closed issues: 
     3023  <list style="symbols">  
     3024    <t> 
     3025      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/285"/>: 
     3026      "Strength of requirements on Accept re: 406" 
     3027    </t> 
     3028  </list> 
    30143029</t> 
    30153030</section> 
    30163031