401 and 403 errors treated indistinguishably by client
Bug #956513 reported by
Gabriel Hurley
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Glance |
Fix Released
|
High
|
Gabriel Hurley | ||
Bug Description
Glance's client code treats status codes 401 (Not Authorized) and 403 (Forbidden) as the same error, and consequently raises the same exception for each: https:/
This is inappropriate, as the two are distinct errors with different meanings, and different actions need to be taken for each. The key distinction being that with a 401 you might be able to complete the request with proper authorization, whereas with 403 "Authorization will not help and the request SHOULD NOT be repeated." (from the W3C spec).
Without distinct exceptions in the client this can't be respected by any handler.
| Changed in glance: | |
| assignee: | nobody → Gabriel Hurley (gabriel-hurley) |
| status: | New → Confirmed |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to glance (master) | #1 |
| Changed in glance: | |
| status: | Confirmed → In Progress |
| Changed in glance: | |
| milestone: | none → essex-rc1 |
| Changed in glance: | |
| importance: | Undecided → High |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to glance (master) | #2 |
| Changed in glance: | |
| status: | In Progress → Fix Committed |
| Changed in glance: | |
| status: | Fix Committed → Fix Released |
| Changed in glance: | |
| milestone: | essex-rc1 → 2012.1 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/