Fix cross-domain cookie handling and domain rebinding#1553
Fix cross-domain cookie handling and domain rebinding#1553Eugeny merged 13 commits intowarp-tech:mainfrom
Conversation
|
@Eugeny I think this one should be ready to review! |
|
I had a previous PR that fixed only part of the issue (I hadn't realized it at the time until we got it deployed out to our users), but this fixes the other part, and also helps with the overall flow of the domain rebound sites. We've had it running for a few days internally and I didn't hear any issues |
|
We've been running this internally with our users since this PR has been opened, and things have been working as expected without issues on this version |
Eugeny
left a comment
There was a problem hiding this comment.
Thank you for your work and sorry for taking so long to review.
In general, could you please add a few comments outlining the logic of the host/cookie checks? It was a bit hard for me to follow even knowing the code base.
|
@Eugeny made the changes, deployed them internally, and things seem to still be working |
d8f4eba to
2483e4d
Compare
1b2e7d6 to
c4e8f27
Compare
|
@Eugeny rebased and ready! |
|
@Eugeny hate to be a bother, could I get a bump on this though! |
|
Thank you and sorry for taking so long ✌️ |
Co-authored-by: Eugene <[email protected]>
This PR fixes cross-domain cookie handling and improves domain rebinding functionality for HTTP targets.
1. Cross-Domain Cookie Support
warpgate.example.comandfoo.warpgate.example.com)SecureandSameSite=Noneattributes for HTTPS2. Domain Rebinding Improvements
external_hostconfigured, visiting that domain automatically routes to the bound targetUI Fixes
external_hostto ensure correct navigation