Issue metadata
Sign in to add a comment
|
Some cookie-related HTTP headers are not visible in DevTools for cross-domain requests
Reported by
sokolof...@gmail.com,
Dec 9
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36 Steps to reproduce the problem: 1. Create a page that makes a request to another domain that is supposed to get/send cookie 2. Check this request in the network tab 3. You are not able to see Set-Cookie/Cookie headers What is the expected behavior? You should be able to see these cookie-related headers What went wrong? You are not able to see Set-Cookie/Cookie headers In the meantime doing absolutely the same test in Mozilla Firefox I was able to see necessary headers and some more Did this work before? N/A Chrome version: 70.0.3538.110 Channel: stable OS Version: 10.0 Flash Version:
,
Dec 10
,
Dec 11
Thanks for filing the issue... @reporter: Could you please provide a sample file or a URL that reproduces the issue, so that it would be really helpful in triaging the issue.
,
Dec 16
Hi! Thanks for replying and sorry for the delay! It is slightly problematic for me to share the real use case where I have noticed the issue, however, I've managed to reproduce it before submitting this thread. I am attaching the html document that contains a JavaScript code that makes a request to my my heroku-based app that sets the 3rd party cookie. If you going to use it, please be patient since my heroku account is free and the first request can time-out since the app required couple of minutes to wake up from the hibernation mode. Please, let me know of anything else is needed. Thanks
,
Dec 16
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 17
+1, This is very annoying when debug something! It seems related to CORB.
,
Jan 2
,
Jan 11
The issue seems to be similar to issue id: 918322, hence marking it as duplicate and merging into it. Note: Please feel free to undupe the issue if it is not the case. Thanks.! |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by susan.boorgula@chromium.org
, Dec 9