Reviewed:  https://review.openstack.org/325957
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=ce0e16bcc56a3123490db9ca2978633815aa51c6
Submitter: Jenkins
Branch:    feature/crypto

commit e9c9e1870b32ce948e758c01f1cfcf840a720c2c
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://wiki.openstack.org/wiki/Translations/Infrastructure
    
    Change-Id: I0e061ecba6dc215d0d3b12aac14b8d4b08fbc682

commit 886fa0822a7881806fd5b2ac8aa66e0a628da3a8
Author: Thiago da Silva <email address hidden>
Date:   Thu Jun 2 23:02:55 2016 -0400

    update pyeclib and liberasurecode links
    
    Change-Id: Ic6d04083618362778363fea1570caaa865e44557
    Signed-off-by: Thiago da Silva <email address hidden>

commit 6f78646ea2200fa2c5dd424589a6cae537f00deb
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://tools.ietf.org/html/rfc2616#section-9.4
    
    Change-Id: Ie60a6fb632613055da5279db5b128ce5ee5172ae
    Closes-Bug:#1539805

commit 6b0e9a3e2464406743e01a3dd789d30c2bf81a2a
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: Id38182f15bcbfbb145b57cee179a8fd47ec8e2b7

commit e56a1a550aace984c8ec4b422fc884ddc579d2d0
Author: Kota Tsuyuzaki <email address hidden>
Date:   Wed Jun 1 23:53:35 2016 -0700

    pids in probe is no longer used
    
    Change-Id: I1fd76004257a8c05ce8bb1f3ca0e45000509f833

commit 99186aded9d4904f63444eb8d33ab2d1c08eed76
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://wiki.openstack.org/wiki/Translations/Infrastructure
    
    Change-Id: Iaf727e51ab444e8cb6199fda45595fc69497ea2d

commit daae74ca65d945d53c53718b8875322ffe9f9ac4
Author: Nelson Almeida <email address hidden>
Date:   Wed Jun 1 17:29:10 2016 -0300

    Adding sorting_method to admin_guide
    
    Change-Id: I1162f154e3a577a95f9f5ea0e0f723b7df5a4baf

commit 4f053c61d6ea49cf566fd7d3d3b1000f2a7a62b5
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: Iaab883386e125c3ca6b9554389e63df17267a135

commit c1b1a5a0ee18776f035bee59e2faff58ec827b14
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-Container-Update-Override-Size sysmeta so this patch
    fixes the container update due to a POST to use that value instead of
    the Content-Length metadata.
    
    Closes-Bug: #1582723
    Change-Id: Ide7c9c59eb41aa09eaced2acfd0700f882c6eab1

commit 03bf984e304278247fa253696a8edda71d785642
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://tools.ietf.org/html/rfc2616#section-13.9
    [2] http://tools.ietf.org/html/rfc7234#section-4.2.2
    
    Change-Id: Ie8f26b97a124ea220a20800e35e040e4463d82bc
    Closes-Bug: 1502159