Prefer the most specific index authentication policy - #174
Draft
zaniebot wants to merge 1 commit into
Draft
Conversation
zaniebot
force-pushed
the
zb/bughunt200/154-authenticate-never-index-overlap
branch
from
July 16, 2026 03:24
630805d to
035df84
Compare
astral-automations-bot
Bot
force-pushed
the
zb/bughunt200/154-authenticate-never-index-overlap
branch
from
July 23, 2026 14:26
035df84 to
b728955
Compare
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
2 participants
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.
Overlapping index roots use the first hash-set match, so a broader authenticated index can override a nested
authenticate = "never"index and send credentials. Choose the most-specific matching root, preferneveron ties, and reject credentials already attached to the request. uv#11896 introduced this policy to prevent credential leakage, and uv#19154 fixed related path-boundary matching.