Repository navigation
Do not treat a 407 received through a tunnel as a proxy challenge - #917
Merged
arturobernalg merged 1 commit intoNov 1, 2026
Merged
Conversation
ok2c
approved these changes
Nov 1, 2026
Once the CONNECT tunnel is established a 407 comes from the origin. It was evaluated against the proxy auth exchange, which failed with a NullPointerException or IllegalStateException. The response is now returned to the caller as is.
arturobernalg
force-pushed
the
tunnel-407-not-proxy-challenge
branch
from
November 1, 2026 10:00
7e79e7e to
b515e35
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
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.
Once the CONNECT tunnel is established a 407 comes from the origin, not from the proxy. It was evaluated against the proxy auth exchange and failed with
NullPointerException(AuthCacheKeeper#updateCache) orIllegalStateException(AuthenticationHandler). The response is now returned to the caller as is, inProtocolExecandAsyncProtocolExec.Tests added.