swift/test/s3api
Tim Burke 7bf2797799 s3api: Clean up some errors
- SHA256 mismatches should trip XAmzContentSHA256Mismatch errors,
  not BadDigest. This should include ClientComputedContentSHA256 and
  S3ComputedContentSHA256 elements.
- BadDigest responses should include ExpectedDigest elements.
- Fix a typo in InvalidDigest error message.
- Requests with a v4 authorization header require a sha256 header,
  rejecting with InvalidRequest on failure (and pretty darn early!).
- Requests with a v4 authorization header perform a
  looks-like-a-valid-sha256 check, rejecting with InvalidArgument
  on failure.
- Invalid SHA256 should take precedence over invalid MD5.
- v2-signed requests can still raise XAmzContentSHA256Mismatch errors
  (though they *don't* do the looks-like-a-valid-sha256 check).
- If provided, SHA256 should be used in calculating canonical request
  for v4 pre-signed URLs.

Change-Id: I06c2a16126886bab8807d704294b9809844be086
2024-09-03 17:26:41 -07:00
..
__init__.py s3api: Clean up some errors 2024-09-03 17:26:41 -07:00
test_input_errors.py s3api: Clean up some errors 2024-09-03 17:26:41 -07:00
test_mpu.py s3api test for zero byte mpu 2024-03-12 13:48:02 +00:00
test_object_lock.py s3api: Add basic GET object-lock support 2023-10-05 16:38:35 +11:00
test_request_target_style.py Tolerate absolute-form request targets 2023-01-03 12:49:30 -08:00
test_service.py s3api: Implement object versioning API 2020-01-28 14:00:08 -08:00
test_versioning.py replace md5 with swift utils version 2020-12-15 09:52:55 -05:00