cd3095d5b72e6b72ae773916f73f562da6672422
* fix: reject ListMultipartUploads requests that also carry uploadId A bucket GET with both the uploads and uploadId query parameters was routed to ListMultipartUploads and answered with the upload listing. S3 rejects the combination with 400 InvalidArgument, "Conflicting query string parameters: uploadId, uploads". Add an error route for the combination ahead of ListMultipartUploads, the way the object level '?uploads' request is rejected, and enable the REST test that covers it. Fixes #2155 * fix: reject uploads with uploadId for every bucket and object operation Requests carrying both the uploads and uploadId query parameters were only rejected for a bucket GET, so DELETE, PUT, POST and HEAD on the bucket or object paths still ran real operations. S3 rejects the combination for every method on both paths, before authentication and before checking that the bucket exists. Register the error route for all methods on the bucket and object routers right after the CORS middleware is set up, ahead of every other route, and cover each method and path with an integration test.
Description
My contributions to versity/versitygw: 24 commits, 11 merged PRs
345 KiB
0 Stars
1 Watchers
0 Forks
Languages
Go
95.9%
Shell
4.1%