S3Api: handle non-ASCII markers in v1 listings.

Code Issues Proposed changes

Added a test for S3 v1 listings that use URL encoding and have non-ASCII
characters. In the process discovered that the XML schema for
ListBucketResult had a small problem: Delimiter and EncodingType needed
to be reordered.
Change-Id: Ib3124ea079a73a577b86de97657603a64b16f965

This commit is contained in:

Timur Alperovich

2019年05月07日 16:15:59 -07:00

parent e85dda286e

commit dade632b0f

4 changed files with 47 additions and 8 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

2
doc/s3api/rnc/list_bucket_result.rnc

View File

@@ -16,8 +16,8 @@ start =

)

),

element MaxKeys { xsd:int },

element EncodingType { xsd:string }?,

element Delimiter { xsd:string }?,

element EncodingType { xsd:string }?,

element IsTruncated { xsd:boolean },

element Contents {

element Key { xsd:string },

S3Api: handle non-ASCII markers in v1 listings.

2 doc/s3api/rnc/list_bucket_result.rnc Unescape Escape View File

2
doc/s3api/rnc/list_bucket_result.rnc

View File