Object.expires is not correct

Bug #1472773 reported by Brian Curtin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack SDK
Incomplete
Medium
Unassigned

Bug Description

http://developer.openstack.org/api-ref-objectstorage-v1.html#createOrReplaceObject

In object_store, the Object class has an expires parameter that is currently set as a header value but is actually used as a query parameter, and it's called temp_url_expires, taking a timestamp.

Revision history for this message
Terry Howe (thowe-g) wrote :

Well, it isn't just a query parameter, right. I'm a little confused.

Used with temporary URLs to specify the expiry time of the signature as a UNIX Epoch timestamp, which is an integer value. For example, 1390852007 represents Mon, 27 Jan 2014 19:46:47 GMT. For more information about temporary URLs, see OpenStack Object Storage API v1 Reference .

Revision history for this message
Brian Curtin (brian.curtin) wrote :

I'm very confused because I'm not sure why I added it, or where it came from, because nothing called only "expires" is even documented. It's showing up in the docs as a query parameter.

I would not be surprised if the docs are wrong as usual. I'll mark this incomplete so it's a note to take a look at what's really going on.

Changed in python-openstacksdk:
status: Confirmed → Incomplete
Changed in python-openstacksdk:
milestone: 1.0 → none
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.