-
Notifications
You must be signed in to change notification settings - Fork 53
Eliminate per-connection 407 probe for known-auth proxies #182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
rurouni88
wants to merge
17
commits into
samuong:master
Choose a base branch
from
rurouni88:feature-connect-auth-cache
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
69b9fc1
Return tr2.hijack() in stale-cache eviction success path
rurouni88 3d22a32
Repopulate auth cache after stale-eviction re-auth succeeds
rurouni88 8dc49a3
Add comment explaining authCache.Store ordering in stale re-auth path
rurouni88 43590de
Lowercase scheme assertion in TestConnectAuthCache_PopulatesOnFirst407
rurouni88 eb14ca3
Update RFC 7235 references to RFC 9110 in proxy.go
rurouni88 7736d5c
Add TestConnectAuthCache_EvictsOnStale407_ThenSucceeds
rurouni88 d81b935
Add TestConnectAuthCache_NoProbeOnSecondRequest to verify probe suppr…
rurouni88 a745a83
Update connectViaProxy call sites in integration tests to pass cache arg
rurouni88 1de5b48
Wire authCache flush to PAC re-download via onPACUpdate callback
rurouni88 1c8a67d
Fix five code review findings: unlock before callback, lowercase sche…
rurouni88 23f54a5
Fix authCache.Store ordering and stale-once mock to pass EvictsOnStal…
rurouni88 242fd20
Update main.go
rurouni88 86d27ec
Address code review feedback from samuong
rurouni88 6924817
Use defer to unlock mutex and call notify in checkForUpdates
rurouni88 008e35f
Guard onPACUpdate nil check before assigning to notify
rurouni88 0eb260b
Remove stale-cache self-heal path from connectViaProxy
rurouni88 be9a3d7
Remove redundant pointer.
rurouni88 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
iiuc all the tests run the request and then the assertions sequentially, do we need a mutex at all?
if not, maybe we could simplify it by getting rid of the mutex and just accessing the count fields directly in the assertions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd recommend keeping it.
The sequential assertion argument only holds if you trust net/http's internal sync chain to substitute for an explicit happens-before guarantee, which isn't what the Go memory model gives you. ServeHTTP runs on its own goroutine, and the increment fires before the response write, so the read in counts() is racing against a goroutine boundary net/http never promised to fence for you.
The mutex is cheap, race-detector clean, and the conventional pattern for any httptest.Server handler touching shared state, and removing it trades a clear guarantee for an implicit one.