Update CHANGELOG and AUTHORS for v1.10
Change-Id: Ie9adff344363f3e57fd3c10c96ed269e0574e95b
This commit is contained in:
parent
f4e248e838
commit
4e69e46630
3
AUTHORS
3
AUTHORS
@ -26,3 +26,6 @@ Vil Surkin <mail@vills.me>
|
|||||||
Wyllys Ingersoll <wyllys.ingersoll@evault.com>
|
Wyllys Ingersoll <wyllys.ingersoll@evault.com>
|
||||||
charz <charles0126@gmail.com>
|
charz <charles0126@gmail.com>
|
||||||
Виль Суркин <vills@vills-pro.local>
|
Виль Суркин <vills@vills-pro.local>
|
||||||
|
Jaivish Kothari <janonymous.codevulture@gmail.com>
|
||||||
|
Kazuhiro MIYAHARA <miyahara.kazuhiro@lab.ntt.co.jp>
|
||||||
|
Sivasathurappan Radhakrishnan <siva.radhakrishnan@intel.com>
|
||||||
|
26
CHANGELOG
26
CHANGELOG
@ -1,3 +1,29 @@
|
|||||||
|
Swift3 (1.10)
|
||||||
|
|
||||||
|
* Supported Python minimum version bumped to 2.7
|
||||||
|
|
||||||
|
* S3Timestamp to ensure the transaction timestamp in Swift3
|
||||||
|
|
||||||
|
- Sometimes Swift3 needs X-Timestamp value to show the request
|
||||||
|
result to the client as the response body (e.g. copy result).
|
||||||
|
However, older versions of swift3 don't have the way to decide
|
||||||
|
the request timestamp. This stuff allows Swift3 to make its own
|
||||||
|
timestamp when a request coming and supports a format which fits
|
||||||
|
to S3 xml format.
|
||||||
|
|
||||||
|
* Fix URL-encoded x-amz-copy-source
|
||||||
|
|
||||||
|
- Fix a bug encoding again URL-encoded x-amz-copy-source.
|
||||||
|
|
||||||
|
* Ignore Content-Type for Delete object request
|
||||||
|
|
||||||
|
- A standard S3 client may set a header "Content-Type" into a DELETE
|
||||||
|
request and it causes unexpected error in the backend pure Swift.
|
||||||
|
To solve this, now swift3 drops the Content-Type header from the
|
||||||
|
request only when it's a DELETE object request.
|
||||||
|
|
||||||
|
* Other minor bug fixes and small improvements
|
||||||
|
|
||||||
Swift3 (1.9)
|
Swift3 (1.9)
|
||||||
|
|
||||||
* Date Header fixes (closes CVE-2015-8466)
|
* Date Header fixes (closes CVE-2015-8466)
|
||||||
|
Loading…
Reference in New Issue
Block a user