New issue
Advanced search Search tips

Issue 911613 link

Starred by 1 user
Status: Verified
Owner:
jarhar@chromium.org
Closed: Dec 17
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Network tab: cors fetch end up in "other" tab instead of XHR

Reported by mmussm...@gmail.com, Dec 4 
UserAgent: 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. Setup a CORS endpoint (E.g. https://getsandbox.com)
2. Do a cors fetch request against the endpoint
3. Check devtools network XHR

What is the expected behavior?
I would expect that both the OPTIONS request and subsequence fetch request is shown under XHR

What went wrong?
The followup request is put into "Other"

Did this work before? N/A 

Chrome version: 70.0.3538.110  Channel: stable
OS Version: 10.0
Flash Version: 

The example is a PUT request but seems to happen consistently regardless of type.
Capture.PNG
18.4 KB View Download
Capture_options.PNG
8.4 KB View Download
Capture_put.PNG
7.8 KB View Download

Comment 1 by alph@chromium.org, Dec 4

Components: -Platform>DevTools Platform>DevTools>Network
Owner: jarhar@chromium.org
Summary: Network tab: cors fetch end up in "other" tab instead of XHR (was: Netowork tab: cors fetch end up in "other" tab instead of XHR)

Comment 2 by swarnasree.mukkala@chromium.org, Dec 4

Labels: Needs-Triage-M70

Comment 3 by paulir...@chromium.org, Dec 5

Status: Assigned (was: Unconfirmed)

Comment 4 by jarhar@chromium.org, Dec 17

Status: Fixed (was: Assigned)
This should be fixed as of version 71. Can you try to reproduce?

Comment 5 by mmussm...@gmail.com, Dec 18 

It's working now.

Comment 6 by jarhar@chromium.org, Dec 18

Status: Verified (was: Fixed)
►

Sign in to add a comment