Open Bug 1474303 Opened 6 years ago Updated 2 years ago

PUT headers not visible in developer tools if reload/redirect after request

Categories

(DevTools :: Netmonitor, defect, P3)

62 Branch
defect

Tracking

(firefox62 affected)

Tracking Status
firefox62 --- affected

People

(Reporter: emil.hemdal.em, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180704003137

Steps to reproduce:

Developer tools open, networking tab, view all, persist logs active.
Initiate a PUT operation using a website that returned status 200 and then automatically reloads the page. (If I disable the reload the request is displayed correctly)


Actual results:

Headers of the request are not visible. (they are in Chrome)


Expected results:

Headers of the request should be visible.
Component: Untriaged → Netmonitor
Product: Firefox → DevTools
@emil: can you please provide a test page I could use to reproduce the issue on my machine?

Honza
Flags: needinfo?(emil.hemdal.em)
Priority: -- → P4
(In reply to Jan Honza Odvarko [:Honza] from comment #1)
> @emil: can you please provide a test page I could use to reproduce the issue
> on my machine?
> 
> Honza

I created a repo with a simple Node.js app here: https://github.com/emilhem/put-network-test
Flags: needinfo?(emil.hemdal.em)
(In reply to Jan Honza Odvarko [:Honza] from comment #1)
> @emil: can you please provide a test page I could use to reproduce the issue
> on my machine?
> 
> Honza

Were you able to reproduce the bug? /Emil
Flags: needinfo?(odvarko)
(In reply to Emil Hemdal from comment #3)
> (In reply to Jan Honza Odvarko [:Honza] from comment #1)
> > @emil: can you please provide a test page I could use to reproduce the issue
> > on my machine?
> > 
> > Honza
> 
> Were you able to reproduce the bug? /Emil

Yes, thanks for the test case!

Honza
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(odvarko)
Priority: P4 → P3
Attached file index.html
I am attaching a test case (implemented by Emil Hemdal) directly here so, it's easier to see it.

Honza
When following Emil's instructions here:
https://github.com/emilhem/put-network-test
(you need to run the app through node to see the issue)

I am seeing an error in the Browser console:
[Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIContentSniffer.getMIMETypeFromContent]"  nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)"  location: "JS frame :: resource:///modules/ContentLinkHandler.jsm :: onStopRequest :: line 181"  data: no] 

Michal, do you know what could be the problem here or who to ask for more details?

Honza
Flags: needinfo?(michal.novotny)
(In reply to Jan Honza Odvarko [:Honza] from comment #6)
> When following Emil's instructions here:
> https://github.com/emilhem/put-network-test
> (you need to run the app through node to see the issue)
> 
> I am seeing an error in the Browser console:
> [Exception... "Component returned failure code: 0x80040111
> (NS_ERROR_NOT_AVAILABLE) [nsIContentSniffer.getMIMETypeFromContent]" 
> nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)"  location: "JS frame ::
> resource:///modules/ContentLinkHandler.jsm :: onStopRequest :: line 181" 
> data: no] 
> 
> Michal, do you know what could be the problem here or who to ask for more
> details?
> 
> Honza

I'm not able to reproduce it. But why do you think this error is related to the problem? I don't understand the code in ContentLinkHandler.jsm well but it seems it's favicon related and it probably fails because there is no icon for the site. I guess it fails here https://searchfox.org/mozilla-central/rev/c296d5b2391c8b37374b118180b64cca66c0aa16/image/imgLoader.cpp#2830. Definitely nothing related to the PUT request.
Flags: needinfo?(michal.novotny)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: