* s3: escape raw semicolons before the router matches a route
registerRouter applied EscapeSemicolonsInQuery with router.Use, but mux
runs router middleware only after it has picked the route. Queries()
matchers split pairs on ';', so GET /bucket?uploads;x=1 reached the
multipart listing handler while the handler and the IAM resolver read
uploads%3Bx=1 and saw no uploads subresource. Wrap the S3 router with the
escape so routing and authorization read the same query.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* s3api: report a listing without prefix as s3:prefix "" in policy conditions
The advanced IAM path already sets s3:prefix to "" when a bucket listing
names no prefix, as AWS does, but bucket policies and attached policies
read conditions from ExtractConditionValuesFromRequest, which leaves the
key out. The AWS home-directory policy that grants s3:prefix ["", "home/"]
then denied the root listing, and a Deny keyed on the empty prefix never
applied.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* s3: test the served handler composition for the semicolon escape
Move the escape and the Vectors split into s3Handler so a command test can
send ';' queries through the handler the server actually serves.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* s3: keep the isVectorsRequest doc comment on its function
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>