Open
Bug 1376045
Opened 7 years ago
Updated 2 years ago
webRequest.onHeadersReceived emitted twice on 304 Not Modified response
Categories
(WebExtensions :: Request Handling, defect, P3)
Tracking
(firefox57 wontfix)
UNCONFIRMED
Tracking | Status | |
---|---|---|
firefox57 | --- | wontfix |
People
(Reporter: Will, Unassigned)
Details
(Whiteboard: [webRequest])
Attachments
(1 file)
717 bytes,
application/x-zip-compressed
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:54.0) Gecko/20100101 Firefox/54.0
Build ID: 20170608105825
Steps to reproduce:
1) Extract attached minimal testing webext.
2) > web-ext run --browser-console --start-url https://ftp.mozilla.org/favicon.ico --firefox nightly
3) Ctrl-Shift-E
4) F5
Actual results:
The tab's network monitor confirms the 304 Not Modified response code.
The browser console shows 2 consecutive onHeadersReceived events for the same requestId, 1st with a 304 status code and 2nd with a 200 status code.
Encountered in release channel 54.0 (64-bit) and confirmed in nightly 56.0a1 (2017-06-22) (64-bit), both on Windows 8.1 x64.
Expected results:
The tab's network monitor confirms the 304 Not Modified response code.
The browser console shows only a single onHeadersReceived event, consistent with the webRequest event flow chart shown on MDN.
The same/equivalent steps run in Chrome 59 result in only a single onHeadersReceived event, with status code 200 (again with the tab's network monitor confirming actually receiving a 304 code).
Updated•7 years ago
|
Updated•6 years ago
|
Product: Toolkit → WebExtensions
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•