Issue metadata
Sign in to add a comment
|
iframe Set-Cookie header failed on redirect for 302
Reported by
eldrel...@gmail.com,
Dec 11 2017
|
||||||||||||||||||||||
Issue descriptionChrome Version : 63.0.3239.83 URLs (if applicable) : Other browsers tested: OK - Chrome 62.0.3202.84 What steps will reproduce the problem? (1) Open an iframe to a src that uses a Set-Cookie in response and returns a 302 for redirect (2) Value from Set-Cookie header not included in headers with redirected request What is the expected result? Value from Set-Cookie header in 302 response should be included in headers for the redirected request What happens instead? Value from Set-Cookie header in 302 response is not included in headers for redirected request Please provide any additional information below. Attach a screenshot if possible.
,
Dec 11 2017
Can you follow the instructions at https://dev.chromium.org/for-testers/providing-network-details to obtain a chrome://net-export log and attach it here?
,
Dec 12 2017
,
Dec 12 2017
This is likely a duplicate of issue 696204 (Which contains a lot of detail already - I don't think we need the log)
,
Dec 12 2017
Not able to right now, due to how the page is consumed. I'll see if I have time to create a test page that reproduces the issue. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Dec 11 2017