Repository navigation
fix: secure HTTP redirect handling - #2099
Conversation
There was a problem hiding this comment.
Code Review
This pull request updates the custom redirect strategy to validate and only follow secure HTTPS redirects to Adyen domains for all redirect status codes, rather than restricting this check to 308 status codes. The tests have been updated and expanded to cover 307 redirects and non-HTTPS scenarios. Feedback suggests improving the host validation in isVerifyLocation to correctly handle bare domains and hostnames with a trailing dot.
154749d to
ab1e54b
Compare
|
Hey @visheshupadhyay, thanks for the PR! The One small thing, could you revert the changes from the Gemini bot comment (allowing bare Once that's reverted, happy to merge! |
|
Thanks @ashwaniarya-adyen for the clarification. I reverted the bare-domain and trailing-dot handling, added negative coverage for those cases, and kept the HTTPS validation for all redirects. The branch is updated and the tests pass. Build Run
Test Run
|
Thanks for the quick update @visheshupadhyay! Could you just run |
|
I've applied the requested Spotless formatting changes and pushed them in commit 04484c1. Thanks again for your review! |
04484c1 to
b260cca
Compare




Fixes #2097 and #2098