DevTools incorrectly reports 204 responses
Reported by
b...@sentia.pl,
May 8 2018
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/65.0.3325.181 Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: 1. Open a new window and go to some website (eg. http://httpstat.us/). 3. Open DevTools, open 'Network' tab. 4. Check 'Preserve log'. 5. Type 'http://httpstat.us/204' in the URL bar and press enter. 6. Select the last request in the 'Network' tab and choose 'Timing'. 7. Page shows incorrect alert 'CAUTION: request is not finished yet!' The above steps describes behavior of Google Chrome, Version 66.0.3359.139 (Official Build) (64-bit) on Linux. Chromium Version 65.0.3325.181 (Official Build) Built on Ubuntu, running on Ubuntu 17.10 (64-bit) behaves differently. The request with 204 response is not displayed in the 'Network' tab at all. I'm attaching screenshots from these two browsers. I'm also attaching the pcap file (and two screenshots from Wireshark for a quick overview) with a dump of TCP conversation showing the server response is just fine. What is the expected behavior? The request should be listed in the 'Network' tab and reported as successful. What went wrong? Google Chrome shows the requests, but mark it as 'pending'. Chromium does not show the request at all. Did this work before? N/A Chrome version: 66.0.3359.139 Channel: stable OS Version: Ubuntu 18.04 LTS Flash Version:
,
May 9 2018
,
May 10 2018
Able to reproduce the issue on Windows 10, mac 10.13.3 and Ubuntu 17.10 using chrome reported version #66.0.3359.139 and latest canary #68.0.3425.0. Bisect Information: ===================== Good build: 66.0.3346.0 Bad Build : 66.0.3347.0 Change Log URL: https://chromium.googlesource.com/chromium/src/+log/da651de72deefafe29d81c522234a2557475cc2b..30f8822a37972aabd4b76d4559d1062d6799c9cb From the above change log suspecting below change Change-Id: I73bf0c1dcde8a961860d1f986f3a9f0a64cd8723 Reviewed-on: https://chromium-review.googlesource.com/912400 caseq@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Note: Adding stable blocker for M-66 as it seems to be a recent regression. Please feel free to remove the same if not appropriate. Thanks...!!
,
May 10 2018
,
May 10 2018
*** Bulk Edit *** M67 Stable promotion is coming VERY soon. Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and request a merge into the release branch ASAP. If fix is already merged to M67 and nothing else is pending, pls mark the bug as fixed. Thank you.
,
May 11 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8b66f9ce6dced8ecb247d89105008867a273c698 commit 8b66f9ce6dced8ecb247d89105008867a273c698 Author: Andrey Kosyakov <caseq@chromium.org> Date: Fri May 11 16:23:39 2018 DevTools: report loadingFailed event for nav requests cancelled because of 204 Bug: 840962 Change-Id: I7df6c302cd13a2a0d8085b26cff4e2fa34f6aca0 Reviewed-on: https://chromium-review.googlesource.com/1054358 Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Andrey Kosyakov <caseq@chromium.org> Cr-Commit-Position: refs/heads/master@{#557898} [modify] https://crrev.com/8b66f9ce6dced8ecb247d89105008867a273c698/content/browser/frame_host/navigation_request.cc [add] https://crrev.com/8b66f9ce6dced8ecb247d89105008867a273c698/third_party/WebKit/LayoutTests/http/tests/inspector-protocol/network/navigation-204-loading-failed-expected.txt [add] https://crrev.com/8b66f9ce6dced8ecb247d89105008867a273c698/third_party/WebKit/LayoutTests/http/tests/inspector-protocol/network/navigation-204-loading-failed.js
,
May 11 2018
,
May 11 2018
[Auto-generated comment by a script] We noticed that this issue is targeted for M-67; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-67 label, otherwise remove Merge-TBD label. Thanks.
,
May 11 2018
,
May 11 2018
Decided not to merge to m67 due to low severity. |
||||||||||||||||||||
►
Sign in to add a comment |
||||||||||||||||||||
Comment 1 by b...@sentia.pl
, May 8 2018