s3: Encode continuation & next continuation tokens when asked (#8292)
When url encoding is passed in v2 listing handler, continuationToken and nextContinuationToken needs to be encoded. The reason is that both represents an object name/prefix in Minio server and it could contain a character unsupported by XML specification.master
parent
77dc2031a2
commit
a790877c01
Loading…
Reference in new issue