84eeaa7803
add test for create bucket and put website with streaming signature
6ea6a8d6d1
add test framework for arbitraty S3 requests
4458996ea5
garage_api: Update streaming payload stream unit tests
81f1db6060
garage_api: Handle streaming payload early in request handling
aea8b41728
document request routing logic
trinity-1686a
created branch more-streaming-payload in trinity-1686a/garage
2022-03-11 16:36:10 +00:00
7f14b6c24d
add test framework for arbitraty S3 requests
f2e72bb05e
garage_api: Update streaming payload stream unit tests
a2f49e59d1
garage_api: Handle streaming payload early in request handling
c00b2c9948
Functional tests for admin commands
8df1e186de
Functional tests for website endpoints
3536903a58
re-update cargo.nix
fe9210f071
address review comments
93637d40ec
correct location, response xml and behavior on missing filename
63948190e4
stricter policy validation
e0aee72a9c
fix review comments
Support for PostObject
turns out AWS ignore this, and only consider content type set in what I called param, not in the field metadata
Support for PostObject
this is not specified, it's however the behavior of AWS. policy
and x-amz-signature
are the only two fields I found to not be required in the policy. Even x-amz-credential
, which is definitelly…
Support for PostObject
that was actually how a previous iteration worked. This behavior was added because it's exactly how AWS behave (not that I can say I agree with that behavior)