Do not include Content-Type to presigned URL #505

New issue

Open

opened 2024-09-30 10:54:19 +00:00 by alexvanin · 0 comments

alexvanin commented

2024-09-30 10:54:19 +00:00

Owner

S3 Authmate allows to generate presign URL even for object upload. However, it uses hardcoded Content-Type header in a signature.

req.Header.Set(ContentTypeHdr, "text/plain")

This header is not usable for all cases, so consider change it.

Describe the solution you'd like

As simple solution Content-Type can be dropped from signature at all, so HTTP client can set any value and get correct output.

Describe alternatives you've considered

Provide an option to configure Content-Type header value the same way as Authmate allows to configure lifetime.

Additional context

Also it would be nice to have an example of a curl command to upload file with presigned URL.

## Is your feature request related to a problem? Please describe. S3 Authmate allows to generate presign URL even for object upload. However, it uses hardcoded `Content-Type` header in a signature. https://git.frostfs.info/TrueCloudLab/frostfs-s3-gw/src/commit/6b109eee92e8b7bb00d9071de8d91939a39b609e/api/auth/presign.go#L37 This header is not usable for all cases, so consider change it. ## Describe the solution you'd like As simple solution `Content-Type` can be dropped from signature at all, so HTTP client can set any value and get correct output. ## Describe alternatives you've considered Provide an option to configure `Content-Type` header value the same way as Authmate allows to configure lifetime. ## Additional context Also it would be nice to have an example of a `curl` command to upload file with presigned URL.

👍 1