Skip to content

Conversation

@padamstx
Copy link
Contributor

This commit introduces a new okhttp interceptor that will implement customized behavior for HTTP redirects.
Specifically, "safe" headers will be included in a redirected request if the original and redirected hosts are the same, or are both within IBM's "cloud.ibm.com" domain.

@padamstx padamstx requested review from dpopp07 and pyrooka November 27, 2023 19:19
@padamstx padamstx self-assigned this Nov 27, 2023
@padamstx padamstx force-pushed the custom-redirects branch 4 times, most recently from 82a2ac6 to 4f20699 Compare November 27, 2023 22:23
@padamstx padamstx marked this pull request as ready for review November 27, 2023 22:24
@padamstx padamstx requested review from dpopp07 and pyrooka November 27, 2023 22:24
@padamstx padamstx marked this pull request as draft November 27, 2023 22:43
@padamstx
Copy link
Contributor Author

Put this back into draft status until we get an approval from CISO.

Copy link
Member

@pyrooka pyrooka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks pretty good, I just left some marginal comments.

Comment on lines 121 to 122
entry("Cookie", "chocolate chip"),
entry("Cookie2", "snickerdoodle"),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Haha! 🍪

This commit introduces a new okhttp interceptor that will implement customized behavior for HTTP redirects. Specifically, "safe" headers will be included in a redirected request if the original and redirected hosts are the same, or are both within IBM's "cloud.ibm.com" domain. Signed-off-by: Phil Adams <phil_adams@us.ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants