This document:Public document·View comments·Disposition of Comments·
Nearby:Mobile Web Best Practices Working Group Other specs in this tool Mobile Web Best Practices Working Group's Issue tracker
Quick access to LC-1854 LC-1855 LC-1856 LC-1857 LC-1858 LC-1859 LC-1896 LC-1897 LC-1898 LC-1899 LC-1900 LC-1901 LC-1902 LC-1903 LC-1904 LC-1905 LC-1906 LC-1907 LC-1908 LC-1909
Previous: LC-1855 Next: LC-1857
Jo Rabin schreef: > > Laurens > > > > Thanks for your further reply on this. Ref RFC2616 > > > > Accept headers *can* be used to specify certain media > > types which are acceptable for the response. … > > > > Not “should†or “mustâ€. > I think you’re misinterpreting that sentence, it “can†be used because the Accept header is optional. It does not imply the Accept header can be used differently than described, and that you can just put any kind of nonsense in there and still expect it to work. > And if the server needs to respond with a 3xx, 4xx or 5xx response > code, in principle it would not know how to do that if the request did > not contain a range of content types. > I don’t understand how that would be. Different content types are just different representations of data. A single resource can be represented by several content types. If you’re going to indicate to the server that you accept certain representations, then the server can send any of them. However regardless of the content type, the server knows perfectly well when a response of 3xx, 4xx or 5xx is needed for that resource (e.g. when it has moved or is unavailable). They’re two separate things, and unrelated. I do not understand the resistance against just sending the correct Accept headers. That is how the protocol is designed, and it’s also how browsers implement it. Also, you’re completely glossing over my statement that sending incorrect Accept headers *breaks* servers which correctly handle content negotiation, because the accepted content types are not correctly indicated by the test. Thus, with this test the W3C would force web sites to not use content negotiation if they want to get your label for ‘correctness’.