1428942 - Net Console not showing cached calls

Status: RESOLVED WORKSFORME

(DevTools :: Netmonitor, defect, P3)

Description

[Yves Dorfsman]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20171227151400

Steps to reproduce:

* press F12 (to show Network Console)
* ensure "Persist Logs" is enabled
* go to "http://google.com"



Actual results:

The first link showed in the Net Console is a 200 for https://www.google.com - The console does not show the original request. It does not show any 201/302/307.


Expected results:

We should be able to see the original request to http, the 301 or 302 to https etc... This is how is used to work before FF 57 when Persist Logs was enabled.

Comment 1

[Yves Dorfsman]

The same behaviour can be observed on Linux Firefox 57.0.3 and Windows Firefox 57.0.4.

Comment 2

[Asif Youssuff]

Attachment: 57.0.4 linux.png

I can't reproduce this in Firefox 57.0.4 on Linux.

Comment 3

[Nicolas Chevobbe [:nchevobbe]]

Hello Yves, thanks for reporting :)

I have a couple of questions : 
- does the network logs from the console differ from the entries in the netmonitor ? We are using the same code so we should not
- would you have a better test page in which we can see the source more easily ?

Thanks !

Comment 4

[Yves Dorfsman]

I looked more into it, the issue is n0t redirect, but content from cache.

Firefox used to show network calls for which answers are coming from cache, but I can no longer see them on v57.

Chrome still shows "(from disk cache)", while Firefox does not show anything.

To recreate:

* open a fresh browser, open network console, go to "http://api.zioup.com"
  ==> shows 302 to https, and the 200 from the http page
* open a new tab, open network console, go to "http://api.zioup.com" again
  ==> The page is displayed, but nothing is displayed in the network console.

Comment 5

[Yves Dorfsman]

Attachment: chrome showing (from disk cache)

Image showing that Chromium shows "(from disk cache)" when content comes from cache, which Firefox used to, too, but no longer do. You need to go to the page a second time to observe this behaviour.

Comment 6

[Nicolas Chevobbe [:nchevobbe]]

Thanks a lot Yves for the reduced test case. I'm moving the bug under the netmonitor component

Comment 7

[Asif Youssuff]

Yves, I can't reproduce in Firefox stable on Linux -- can you check your about:config to see if devtools.netmonitor.persistlog is set to true? I assume it must be, since Persist Logs button checks that for me. 

I see in the second tab a cached 301, followed by a 200.

Comment 8

[Yves Dorfsman]

Yes, about:config is the first thing I checked, it is set to true.

Is there a setting to display/hide cached responses?

Is there a log or something I can capture when it happens?

BTW, if I keep doing it (opening tabs, open net console, go to "http://api.zioup.com"), I manage to see the cached 301 once in a while. I wonder if it has to do with the 200 being cached too...

Comment 9

[Asif Youssuff]

Sorry, I am not a Firefox developer, I just came across your ticket and tried to triage a bit, was hoping I could find a regression window or fix window -- but I have been unable to reproduce your STR.

Comment 10

[Yves Dorfsman]

I am no longer able to reproduce this issue with Firefox 65.0.1.
It shows the first 301 as a cached call, as expected.

I think this is fixed and can be closed.

Comment 11

[Jan Honza Odvarko [:Honza] (always need-info? me)]

According to the last comment this is not an issue anymore, closing.

Honza