From a790877c010a2ac119252df56c078c2a0c122f87 Mon Sep 17 00:00:00 2001 From: Anis Elleuch Date: Tue, 24 Sep 2019 01:00:53 +0100 Subject: [PATCH] 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. --- cmd/api-response.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cmd/api-response.go b/cmd/api-response.go index 1c72d7c24..088307b6c 100644 --- a/cmd/api-response.go +++ b/cmd/api-response.go @@ -498,8 +498,8 @@ func generateListObjectsV2Response(bucket, prefix, token, nextToken, startAfter, data.Delimiter = s3EncodeName(delimiter, encodingType) data.Prefix = s3EncodeName(prefix, encodingType) data.MaxKeys = maxKeys - data.ContinuationToken = token - data.NextContinuationToken = nextToken + data.ContinuationToken = s3EncodeName(token, encodingType) + data.NextContinuationToken = s3EncodeName(nextToken, encodingType) data.IsTruncated = isTruncated for _, prefix := range prefixes { var prefixItem = CommonPrefix{}