get_object does not allow user-provided headers
Bug #1051046 reported by
David Kranz
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-swiftclient |
Fix Released
|
Wishlist
|
Matthieu Huin | ||
Bug Description
For example, a user may want to provide a "Range" header or other headers documented in the Swift API reference.
| Changed in python-swiftclient: | |
| status: | New → Confirmed |
Revision history for this message
| Darrell Bishop (darrellb) wrote | #1 |
Revision history for this message
| David Kranz (david-kranz) wrote | #2 |
Revision history for this message
| David Kranz (david-kranz) wrote | #3 |
| Changed in python-swiftclient: | |
| importance: | Undecided → Wishlist |
Revision history for this message
| Byron McCollum (byron-mccollum) wrote | #4 |
| Changed in python-swiftclient: | |
| assignee: | nobody → Matthieu Huin (mhu-s) |
| Changed in python-swiftclient: | |
| status: | Confirmed → In Progress |
Revision history for this message
| Fabien Boucher (fabien-boucher) wrote | #5 |
| Changed in python-swiftclient: | |
| status: | In Progress → Fix Committed |
| Changed in python-swiftclient: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
cf. http://
I see the following set of potentially-desired headers:
* If-Match
* If-None-Match
* If-Modified-Since
* If-Unmodified-Since
* Range (partially supported)
We could add support for them to get_object in the same way additional headers are supported in put_object (i.e. as optional keyword args, with good defaults, and potentially additional handling before marshaling into actual header values).