Closed
Conversation
Co-authored-by: drk1wi <2052966+drk1wi@users.noreply.github.com>
Copilot
AI
changed the title
Fix multi-origin proxy translation paths
Fix multi-origin translation paths in proxy
Aug 14, 2026
Copilot created this pull request from a session on behalf of
drk1wi
August 14, 2026 14:09
View session
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.
The proxy translation logic was previously mishandling multi-origin setups by using
Header.Get()(which drops all but the first header value) and by unconditionally overriding the backend's CORS headers with the client's origin.Changes
Origin,Referer,Cookie,WWW-Authenticate, andAccess-Control-Allow-Originto iterate over all header values (Header["Name"]) rather than just the first one.Access-Control-Allow-Originpatching to translate backend-provided origins (usingRealURLtoPhish) instead of blindly forcing it to the client's request origin. This correctly preserves dynamic multi-origin configurations from the backend.OriginandAccess-Control-Allow-Credentials: trueonly if the backend server does not provide anAccess-Control-Allow-Originheader.