Comment 11 for bug 1539805
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to swift (feature/hummingbird) | #11 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: feature/hummingbird
commit 88dbbe88bb8bc77
Author: John Dickinson <email address hidden>
Date: Wed Jun 1 15:46:32 2016 -0700
AUTHORS/
Change-Id: I0dba970b297013
commit e9c9e1870b32ce9
Author: OpenStack Proposal Bot <email address hidden>
Date: Fri Jun 3 06:49:09 2016 +0000
Imported Translations from Zanata
For more information about this automatic import see:
https:/
Change-Id: I0e061ecba6dc21
commit 886fa0822a78818
Author: Thiago da Silva <email address hidden>
Date: Thu Jun 2 23:02:55 2016 -0400
update pyeclib and liberasurecode links
Change-Id: Ic6d04083618362
Signed-off-by: Thiago da Silva <email address hidden>
commit 6f78646ea2200fa
Author: Sivasathurappan Radhakrishnan <email address hidden>
Date: Thu Mar 17 09:40:23 2016 +0000
Add content-disposition header to tempurl request
Added content-disposition header to HEAD tempurl request.
As per HTTP docs[1] HEAD response must be identical to GET
except return message-body response.
[1]https:/
Change-Id: Ie60a6fb6326130
Closes-
commit 6b0e9a3e2464406
Author: Tim Burke <email address hidden>
Date: Thu Jun 2 16:49:32 2016 +0000
Remove unused (but defaulted) args
Every time we call start_server, check is True.
Every time we call check_server, we use the default timeout.
Change-Id: Id38182f15bcbfb
commit e56a1a550aace98
Author: Kota Tsuyuzaki <email address hidden>
Date: Wed Jun 1 23:53:35 2016 -0700
pids in probe is no longer used
Change-Id: I1fd76004257a8c
commit 99186aded9d4904
Author: OpenStack Proposal Bot <email address hidden>
Date: Thu Jun 2 06:41:44 2016 +0000
Imported Translations from Zanata
For more information about this automatic import see:
https:/
Change-Id: Iaf727e51ab444e
commit daae74ca65d945d
Author: Nelson Almeida <email address hidden>
Date: Wed Jun 1 17:29:10 2016 -0300
Adding sorting_method to admin_guide
Change-Id: I1162f154e3a577
commit 4f053c61d6ea49c
Author: Félix Cantournet <email address hidden>
Date: Wed Apr 27 22:17:01 2016 +0200
Fix swift-dispersion in multi-region setups
If you have 2 swift regions served by the same keystone,
then the client cannot get the correct URL for the swift endpoint
without specifying a region_name.
Closes-Bug: 1587088
Change-Id: Iaab883386e125c
commit 86e9e827bab7bed
Author: John Dickinson <email address hidden>
Date: Tue May 31 11:27:43 2016 -0700
add explicit HA info to the deployment guide
Change-Id: I7614952c523080
commit a54095e562c2a14
Author: Ondřej Nový <email address hidden>
Date: Tue May 31 17:00:30 2016 +0200
swift-
This option assume a yes response to all questions. It is usefull for
scripts.
Change-Id: I28ca1a44507e0f
commit a821dd42de1762e
Author: Tim Burke <email address hidden>
Date: Thu May 26 13:42:12 2016 -0700
Don't include holes when reporting how many devices a ring has
Change-Id: I9b933051aec009
commit c1b1a5a0ee18776
Author: Alistair Coles <email address hidden>
Date: Tue May 17 14:22:05 2016 +0100
Send correct size in POST async update for EC object
When a PUT request is made to an EC object the resulting container
update must include the override values for the actual object
etag and size, as opposed to the fragment etag and size. When a POST
request is made the same override values should be included in the
container update, but currently the update includes the incorrect EC
fragment size (but the correct body etag).
This is ok so long as the update for the object PUT request arrives at
the container server first (whether by direct update or replication)
because the etag and size values in an update due to an object POST
will not have a newer timestamp that the PUT and will therefore be
ignored at the container server.
However, if the update due to the object PUT request has not arrived
at the container server when the update due to the object POST
arrives, then the etag and incorrect size sent with the POST update
will be recorded in the container server. If the update due to the PUT
subsequently arrives it will not fix this error because the timestamp
of its etag and size values is not greater than that of the already
recorded values.
Fortunately the correct object body size is persisted with the object
as X-Backend-
fixes the container update due to a POST to use that value instead of
the Content-Length metadata.
Closes-Bug: #1582723
Change-Id: Ide7c9c59eb41aa
commit 03bf984e3042782
Author: Tim Burke <email address hidden>
Date: Fri Feb 12 10:15:31 2016 -0800
Add Expires header for successful GETs using tempurls
This allows caches to actually use the expiration time that's already
embedded in the URL.
From RFC 2616 [1]:
> [S]ince some applications have traditionally used GETs and HEADs with
> query URLs (those containing a "?" in the rel_path part) to perform
> operations with significant side effects, caches MUST NOT treat
> responses to such URIs as fresh unless the server provides an explicit
> expiration time.
However, RFC 7234 notes that this hasn't played out in practice [2]:
> Note: Section 13.9 of [RFC2616] prohibited caches from calculating
> heuristic freshness for URIs with query components (i.e., those
> containing '?'). In practice, this has not been widely implemented.
> Therefore, origin servers are encouraged to send explicit directives
> (e.g., Cache-Control: no-cache) if they wish to preclude caching.
[1] http://
[2] http://
Change-Id: Ie8f26b97a124ea
Closes-Bug: 1502159