Files
seaweedfs/weed
chrislu 394847a621 fix: add CORS preflight handler to S3 API test infrastructure
The TestS3CORSWithJWT test was failing because our lightweight test setup
only had a /test-auth endpoint but the CORS test was making OPTIONS requests
to S3 bucket/object paths like /test-bucket/test-file.txt.

### Problem:
- CORS preflight requests (OPTIONS method) were getting 404 responses
- Test expected proper CORS headers in response
- Our simplified router didn't handle S3 bucket/object paths

### Solution:
- Added PathPrefix handler for /{bucket} routes
- Implemented proper CORS preflight response for OPTIONS requests
- Set appropriate CORS headers:
  - Access-Control-Allow-Origin: mirrors request Origin
  - Access-Control-Allow-Methods: GET, PUT, POST, DELETE, HEAD, OPTIONS
  - Access-Control-Allow-Headers: Authorization, Content-Type, etc.
  - Access-Control-Max-Age: 3600

### Test Results:
 TestS3CORSWithJWT: Now passes (was failing with 404)
 TestS3EndToEndWithJWT: Still passes (13/13 tests)
 TestJWTAuthenticationFlow: Still passes (6/6 tests)

The CORS handler properly responds to preflight requests while maintaining
the existing JWT authentication test functionality.
2025-08-24 21:00:38 -07:00
..
2025-08-09 21:47:29 -07:00
2025-07-19 23:56:17 -07:00
2025-08-21 08:28:07 -07:00
2025-08-22 01:15:42 -07:00
2025-08-22 01:15:42 -07:00
2024-06-25 09:18:11 -07:00
2024-02-14 08:26:38 -08:00
2025-08-21 08:28:07 -07:00
2025-08-21 08:28:07 -07:00
2025-07-19 21:43:34 -07:00
2025-03-17 23:13:27 -07:00