Should raise 413 when image size exceeded
Bug #1158711 reported by
Stuart McLaren
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Glance |
Fix Released
|
Medium
|
Stuart McLaren | ||
Bug Description
We should probably raise a 413 rather than HTTPBadRequest when an attempt to upload a 'too large' image is made:
| Changed in glance: | |
| assignee: | nobody → Stuart McLaren (stuart-mclaren) |
| status: | New → In Progress |
| Changed in glance: | |
| importance: | Undecided → Medium |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to glance (master) | #1 |
| Changed in glance: | |
| status: | In Progress → Fix Committed |
| Changed in glance: | |
| milestone: | none → havana-1 |
| status: | Fix Committed → Fix Released |
| Changed in glance: | |
| milestone: | havana-1 → 2013.2 |
To post a comment you must log in.
Reviewed: https:/
Committed: http://
Submitter: Jenkins
Branch: master
commit 91f538f53dc4434
Author: Stuart McLaren <email address hidden>
Date: Fri Mar 22 11:19:06 2013 +0000
Return 413 when image_size_cap exceeded
HTTP Error 413 (Request entity too large) may be the most appropriate
response when a request to upload an image whose size exceeds
image_size_cap is made.
Addresses bug 1158711.
Change-Id: I4abcb3a8b57c08