Does pre-signed POST uploads support metadata fields?
āQuestion
Iām doing browser uploads using a POST policy. The upload itself succeeds perfectly, but I've noticed that my custom metadata (x-amz-meta-* fields) isn't being saved to the object, even though it's correctly included in both the policy conditions and the form data.
I was looking at following docs, which made me think POST uploads would support metadata as in the example "x-amz-meta-uuid" is used : https://www.tigrisdata.com/docs/objects/upload-via-html-form/
Can anyone confirm if custom metadata is supported for POST uploads, or is this a known limitation on the backend? (I know PUT works, just specifically wondering about POST).
I was looking at following docs, which made me think POST uploads would support metadata as in the example "x-amz-meta-uuid" is used : https://www.tigrisdata.com/docs/objects/upload-via-html-form/
Can anyone confirm if custom metadata is supported for POST uploads, or is this a known limitation on the backend? (I know PUT works, just specifically wondering about POST).
Tigris facilitates the posting of objects via HTTP, which proves beneficial in
Solution
There was a bug on our end that was causing this issue. We've fixed it, and metadata fields now work correctly for POST uploads (same as they do for PUT). Thanks for reporting the issue, and sorry for any inconvenience caused.
