Closed
Bug 802879
Opened 12 years ago
Closed 12 years ago
Bagheera uses HTTP 406 improperly
Categories
(Mozilla Metrics :: Metrics Data Ping, defect)
Mozilla Metrics
Metrics Data Ping
Tracking
(Not tracked)
RESOLVED
FIXED
Unreviewed
People
(Reporter: gps, Unassigned)
References
Details
Bagheera is currently using HTTP 406 (Not Acceptable) improperly. From httpbis (the eventual RFC 2616 successor):
https://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-21#section-7.5.6
The resource identified by the request is only capable of generating
response representations which have content characteristics not
acceptable according to the Accept and Accept-* header fields sent in
the request.
In short, 406 involves Accept* headers. Bagheera is using "Not Acceptable" in the English meaning of the words, not what the spec defines.
HTTP 400 or 200 + an error in the response document are acceptable alternatives.
See http://docs.services.mozilla.com/storage/apis-2.0.html for an HTTP API that does things properly.
Reporter | ||
Updated•12 years ago
|
Group: metrics-private
Comment 1•12 years ago
|
||
This is fixed and deployed. It will now return a 400 Bad Request instead of a 406.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•