Comment 2 for bug 1678022

Revision history for this message
Mat Mannion (mat-mannion) wrote :

@donagh-mccabe it's a little difficult to read, but the content of the manifest file is in my initial report. I've prettified it for readability:

[{
 "path": "slo-test/Files/OpenOffice.org 3.3 %28en-GB%29 Installation Files/openofficeorg1.cab/slo/1490950292.028000/38547913/0/00000001",
 "etag": "58f06dd588d8ffb3beb46ada6309436b",
 "size_bytes": 33554432
}, {
 "path": "slo-test/Files/OpenOffice.org 3.3 %28en-GB%29 Installation Files/openofficeorg1.cab/slo/1490950292.028000/38547913/0/00000002",
 "etag": "2b4b81733d0a2e4abe89516639627408",
 "size_bytes": 4993481
}]

The key is partially URL-encoded as we are migrating from a filesystem to an object store and we want to maintain the original file names, which is why we're setting the key with the brackets encoded - the only situation where this bug in Swift appears is where there is this encoding. It looks for all intents and purposes like Swift should be handling this correctly, it correctly receives the double-encoded brackets for each part but then sends a 400 for the manifest file.