Skip to content

Respect explicit opt out for Expect: 100-continue even on cross region calls - #7204

Merged
RanVaknin merged 2 commits into
masterfrom
rvaknin/honor-expect-continue-cross-region
Jul 30, 2026
Merged

Respect explicit opt out for Expect: 100-continue even on cross region calls#7204
RanVaknin merged 2 commits into
masterfrom
rvaknin/honor-expect-continue-cross-region

Conversation

@RanVaknin

@RanVaknin RanVaknin commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Closes: #7081


In #7057 we forced enable the Expect: 100-continue when S3 cross region calls are made (even when the setting was explicitly disabled). Without the header, the service would close the connection before the body of the request was sent, resulting in an IOException instead of the expected 3xx status code needed for the implicit redirect.

This PR makes the interceptor honor an explicit expectContinueEnabled(false) on cross region calls. The header is still included by default for cross region calls, so users who don't opt out are unaffected.
Only an explicit false disables it. When that happens on a cross region request, we emit a DEBUG log informing the user of this risk.

@RanVaknin RanVaknin changed the title Respect explicit opt out for Expect: 100-continue even on cross regio… Respect explicit opt out for Expect: 100-continue even on cross region calls Jul 29, 2026
@RanVaknin RanVaknin added the no-api-surface-area-change Indicate there is no API surface area change and thus API surface area review is not required label Jul 29, 2026
@RanVaknin
RanVaknin marked this pull request as ready for review July 29, 2026 20:37
@RanVaknin
RanVaknin requested a review from a team as a code owner July 29, 2026 20:37
@RanVaknin
RanVaknin added this pull request to the merge queue Jul 29, 2026
Merged via the queue into master with commit c03130e Jul 30, 2026
12 of 13 checks passed
@github-actions

Copy link
Copy Markdown

This pull request has been closed and the conversation has been locked. Comments on closed PRs are hard for our team to see. If you need more assistance, please open a new issue that references this one.

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Jul 30, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

no-api-surface-area-change Indicate there is no API surface area change and thus API surface area review is not required

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Honor expect-100 disabling rather than turn it on from independent settings

2 participants