User talk:Infinity Linden/OGP Serialization And Transport: Difference between revisions
Jump to navigation
Jump to search
Which Linden (talk | contribs) New page: I think 406 is the proper response code if the client sends an Accept header with values you don't support. 415 is for when the body of a request is in a content-type that the server cann... |
Which Linden (talk | contribs) Formatting |
||
| Line 1: | Line 1: | ||
I think 406 is the proper response code if the client sends an Accept header with values you don't support. 415 is for when the body of a request is in a content-type that the server cannot parse (e.g. trying to post application/x-www-form-urlencoded data when we only parse llsd). | I think 406 is the proper response code if the client sends an Accept header with values you don't support. 415 is for when the body of a request is in a content-type that the server cannot parse (e.g. trying to post application/x-www-form-urlencoded data when we only parse llsd). | ||
406: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.7 | * 406: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.7 | ||
415: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.16 | * 415: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.16 | ||
[[User:Which Linden|Which Linden]] | [[User:Which Linden|Which Linden]] 18:18, 29 September 2008 (PDT) | ||
Latest revision as of 18:18, 29 September 2008
I think 406 is the proper response code if the client sends an Accept header with values you don't support. 415 is for when the body of a request is in a content-type that the server cannot parse (e.g. trying to post application/x-www-form-urlencoded data when we only parse llsd).
- 406: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.7
- 415: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.16
Which Linden 18:18, 29 September 2008 (PDT)