dynamic large object 400s on x-object-manifest value starting with slash

Bug #1191958 reported by David Goetz
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Object Storage (swift)
Invalid
Low
Unassigned

Bug Description

should probably just strip it off

Changed in swift:
importance: Undecided → Low
tags: added: low-hanging-fruit
Revision history for this message
Kun Huang (academicgareth) wrote :

In document and codes, it only says in 'container/prefix' format. If not, return a bad request with body "X-Object-Manifest must in the format container/prefix", I think that's ok.

David Cesiel (dcesiel)
Changed in swift:
assignee: nobody → David Cesiel (dcesiel)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to swift (master)

Fix proposed to branch: master
Review: https://review.openstack.org/40074

Changed in swift:
status: New → In Progress
clayg (clay-gerrard)
Changed in swift:
status: In Progress → Confirmed
assignee: David Cesiel (dcesiel) → nobody
Changed in swift:
assignee: nobody → Richard Hawkins (richard-hawkins)
assignee: Richard Hawkins (richard-hawkins) → nobody
Revision history for this message
Andy McCrae (andrew-mccrae) wrote :

This shouldn't be seen as a bug - the response shows that a leading slash isn't the correct format - swift shouldn't account for format errors - aside from to let the user know the correct format, which it already does. Changing the code to allow a leading / to be "ignored" seems the incorrect approach.

Changed in swift:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.