Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Spike] Investigate removing proxy correlation #29386

Open
mschile opened this issue Apr 23, 2024 · 0 comments
Open

[Spike] Investigate removing proxy correlation #29386

mschile opened this issue Apr 23, 2024 · 0 comments
Labels
type: chore Work is required w/ no deliverable to end user

Comments

@mschile
Copy link
Contributor

mschile commented Apr 23, 2024 •
edited

Proxy correlation has been difficult to get correct due to the many different scenarios of when a browser pre-request is sent. This has been made even more difficult now that we are monitoring service workers. If possible, we should re-evaluate whether or not proxy correlation is needed. The main reason we use proxy correlation is to receive the resource type which is used in the following locations:

  • Proxy-logging
  • ResourceTypeAndCredentialManager
  • MaybeEndWithEmptyBody
@jennifer-shehane jennifer-shehane added the type: chore Work is required w/ no deliverable to end user label Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: chore Work is required w/ no deliverable to end user
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jennifer-shehane @mschile