Timeline for Why doesn't the HTML\DOM specification allow hyperlinks to set an accept header?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 2, 2017 at 19:49 | comment | added | Jules Sam. Randolph | What it is definitely not meant to do, however, is link to a specific representation of a resource. That is for the client and server to negotiate, and the server to ultimately decide. → And what if the application designer wants to take part to the negotiation ? Is there any reference where it is asserted that the user agent i.e. client must be and only is the web browser ? I would be glad if you could help me understand this. | |
| Feb 2, 2017 at 19:41 | comment | added | Jules Sam. Randolph | If a client specifies application/xml and the server only supports application/json, then the server is going to send back JSON - not XML. Then, what is 406 HTTP error for ? To quote rfc2616 : If an Accept header field is present, and if the server cannot send a response which is acceptable according to the combined Accept field value, then the server SHOULD send a 406 (not acceptable) response. | |
| Jul 30, 2014 at 9:09 | history | bounty awarded | Andy Hunt | ||
| Jul 29, 2014 at 18:50 | history | answered | Aaronaught | CC BY-SA 3.0 |