740356 - Show cached headers for each resource

Status: NEW

(DevTools :: Netmonitor, defect, P3)

Description

[Anthony Ricaud (:rik)]

In the Inspect Network Request window, Content-Type for this resource is missing.

The resource is sending "Content-Type: text/plain; charset=UTF-8"

I suspect the charset part might trigger a bug in the code.

Comment 1

[Mihai Sucan [:msucan]]

Thanks for your report! Can you please tell me more about the system you use for testing? Which build do you try?

I just tried Firefox 12 Beta coming from the Ubuntu Firefox team PPA and the Content-Type header is displayed. I also tried a local build I did yesterday from the fx-team repository (Firefox 14 pre-alpha of some sorts): Content-Type shows for me.

Comment 2

[Anthony Ricaud (:rik)]

I'm running Nightly on OS X 10.7.3.

I've confirmed this on Pascal's Ubuntu. I don't remember which version and how he got it though.

Comment 3

[Pascal Chevrel:pascalc]

I run Ubuntu 11.10 and I can confirm that I don't see a Content-type field both on Firefox 11 shipping from Ubuntu and with the latest nightly from Mozilla (Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120329 Firefox/14.0a1)

Pascal

Comment 4

[Mihai Sucan [:msucan]]

What HTTP response do you have? 200 OK or 304 Not modified?

Comment 5

[Pascal Chevrel:pascalc]

Just tested on nightly:

If I try again, I get a 304 and non content-type field

If i CTRL+SHIFT+R the page to force a relead, I get a 200 and the content-type field is there

Comment 6

[Mihai Sucan [:msucan]]

(In reply to Pascal Chevrel:pascalc from comment #5)
> Just tested on nightly:
> 
> If I try again, I get a 304 and non content-type field
> 
> If i CTRL+SHIFT+R the page to force a relead, I get a 200 and the
> content-type field is there

That is expected behavior. The server doesn't send the content-type header when 304 not modified is returned.

Comment 7

[Anthony Ricaud (:rik)]

Yeah, my bad. 

Although, that illustrates a use-case. I'd like to know the Content-Type of a resource, regardless of the presence of the HTTP header.

Comment 8

[Mihai Sucan [:msucan]]

Yes, we need a view for the cached HTTP headers.

Comment 9

[Patrick Brosset <:pbro>]

Inactive for the past 5 years, but still an issue.