Accept headers that fail to parse should trigger 400 Bad Request, not 406 Not Acceptable
Bug #1716509 reported by
Tim Burke
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Any failure to parse the Accept header results in a 406,
even when a 400 may be more appropriate. In particular, when
performing an account or container listing, both
Accept: text/xml;q=foo
and
Accept: text/xml;
...trigger a 406, although text/xml *is* acceptable. Client just doesn't know how to ask for it.
(Kicked out from https:/
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/502845 /git.openstack. org/cgit/ openstack/ swift/commit/ ?id=c118059719d ed85381e9b134b0 91d04a7b5a3955
Committed: https:/
Submitter: Zuul
Branch: master
commit c118059719ded85 381e9b134b091d0 4a7b5a3955
Author: Tim Burke <email address hidden>
Date: Mon Sep 11 22:08:12 2017 +0000
Respond 400 Bad Request when Accept headers fail to parse
Change-Id: I6eb4e4bca95e2e e4fecdb703394cb 2419737922d
Closes-Bug: 1716509