Cover provider redirects in origin acceptance - #48
Merged
ClaudiuSchuster merged 1 commit intoSep 12, 2026
Conversation
ClaudiuSchuster
marked this pull request as ready for review
September 12, 2026 14:32
ClaudiuSchuster
deleted the
oss-oo/provider-redirect-order-60f8-20260912
branch
September 12, 2026 14:32
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An origin HTTP redirect can alter an encoded path before the authored canonical rule runs, even when HTTPS and edge responses are correct. Add a focused regression for the five observed first-hop defects across apex/www and GET/HEAD, and document how to verify the full installed redirect chain.
Provider rule reordering remains a separate operator transition with preserved certificate renewal, exact before/after bindings, original rollback evidence and process-exit recovery. Publication acceptance is unchanged. This follows the failed-and-rolled-back publication of #47.
Validation: complete local repository CI sequence; 34 publication tests with normal and optimized Python; independent source review. Actual provider maintenance and live publication are separate release gates.