Confused by presigned (multipart) upload url messages

1

Hi there,

This is a follow up of my previous (but auto-closed) post Multipart presigned url ‘signature not matching’ message:

I cannot wrap my head around the requirements for generating presigned multipart urls.

What I tried thus far, but failed:

  1. Generate the url and signature based on a (working) single PUT upload, but with partNumber and uploadId included: returns a 403 forbidden and Signature does not match

  2. Generate the url but also include the Content-Type in the signing process: returns a 400 bad request and Query-string authentication version 4 requires the X-Amz-Algorithm, X-Amz-Credential, X-Amz-Signature, X-Amz-Date, X-Amz-SignedHeaders, and X-Amz-Expires parameters. while all parts are present in the generated url

Related: because I add Content-Type to my upload requests for single files, I extended the signing process by including SignedHeaders=content-type;host but this resulted in a Signature does not match error. But with SignedHeaders=host only it does works.

My question: am I doing something wrong or do I miss some hidden requirements? I can provide extra info if needed.

Thanks in advance.

2

Have you tried using R2 real quick to see if multi part works? If so, then it’s likely a tigris issue.

3

Thanks for the suggestion. I will look into that.

4

@hakoptak Unfortunately, presigned urls support for multipart doesn’t exists yet. I have added this as a feature item on our side. Hopefully we should be able to add this support in a few weeks.

5

Hi @himank, that explains a lot. Could you let me know when this feature is testable?

Thanks!

6

@hakoptak I will keep you posted, will also be discussing internally next week about this feature and will let you know about the timelines.

2 Likes
7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.