Cors fetch response in "devtool > network" is put in category "OTHER" instead of "XHR"
Reported by
golo...@gmail.com,
Oct 12
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: 1. Open devtool console in any site other than github.com 2. Evaluate `fetch('https://api.github.com/repositories', {headers: {"content-type": "x"}})` What is the expected behavior? What went wrong? 3. Observe that the filter tab "XHR" contains only the preflight response. Observe that filter tab "Other" contains the "postflight" response with type "json". I am not sure whether this behavior is intentional or not. But I am confused the first time I met it. Did this work before? N/A Chrome version: 69.0.3497.100 Channel: stable OS Version: arch 4.18.12 Flash Version:
,
Oct 12
The "initiator" column is wrong as well. The preflight has the correct initiator, but its missing for the main request. It seems like we should teach devtools enough to show "CORS preflight" for its initiator or type column and get the right info on the main request.
,
Oct 12
,
Dec 17
This should be fixed in chrome 71, can you try to reproduce? wanderview@ you're right about the initiator, I made a separate bug for it: https://bugs.chromium.org/p/chromium/issues/detail?id=915914
,
Dec 18
Yes this is fixed. Thank you.
,
Dec 18
|
||||
►
Sign in to add a comment |
||||
Comment 1 by krajshree@chromium.org
, Oct 12