Skip to content

Fix require_https_for_sse_cpk option not being honored#3364

Open
monkeyWzr wants to merge 2 commits intoaws:version-3from
monkeyWzr:fix_require_https_for_sse_cpk
Open

Fix require_https_for_sse_cpk option not being honored#3364
monkeyWzr wants to merge 2 commits intoaws:version-3from
monkeyWzr:fix_require_https_for_sse_cpk

Conversation

@monkeyWzr
Copy link
Copy Markdown

@monkeyWzr monkeyWzr commented Mar 27, 2026

Fix #2519 (not sure why it is closed).

The require_https_for_sse_cpk config option was documented as a way to disable the HTTPS enforcement for SSE-CPK operations, but the require_https handler method never checked it — the guard always raised regardless of the configured value.

Gate the HTTPS check on context.config.require_https_for_sse_cpk so setting it to false actually allows HTTP endpoints (e.g. for local development against services like MinIO).

Changes:

  • Fix SseCpk plugin to honor require_https_for_sse_cpk config
  • Add specs for HTTPS enforcement, opt-out behavior, and key encoding

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

  The `require_https_for_sse_cpk` config option was documented as a way
  to disable the HTTPS enforcement for SSE-CPK operations, but the
  `require_https` handler method never checked it — the guard always
  raised regardless of the configured value.

  Gate the HTTPS check on `context.config.require_https_for_sse_cpk` so
  setting it to `false` actually allows HTTP endpoints (e.g. for local
  development against services like MinIO).

  Add specs covering the default enforcement behavior, the opt-out, and
  the key base64-encoding/MD5 logic.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

require_https_for_sse_cpk option does not work

1 participant