Because of blobs' number over 1000, there are two requests sent to S3 server when using S3 API Reference ListObjectsV2. But SignatureDoesNotMatch will appear in second request. With help of postman, I found the uriencoded result of continuation-token value leads to the error. Because continuation-token includes character "+" and "&". According to S3 API Reference Authenticating Requests (AWS Signature Version 4), queryparameter should be encoded. "+" is encoded into "%2B", and "&" which is between two queryparameters should not be encoded. But in the result of postman, I found "+" is encoded to "%20" and "&" which is between two queryparameters is encoded to "& amp;"(please ignore the space. I hava to add a space for displaying normally). Has anyone encountered this and somehow resolved this before

I'm trying to do a listobjectsv2 call to the s3 server through API using http requests