432226 - Option to show HTTP headers in view source

Status: VERIFIED WONTFIX

(Camino Graveyard :: General, enhancement)

Description

[Chris Lawson (gone)]

From #camino this morning, edited somewhat for brevity:

[9:20am] <andIIng> is there a way to see headers of a page in Camino ?
[9:21am] <cl> no; I usually use 'curl -I URL' on the command line to do that
[9:22am] <andIIng> but it'd be more comfortable have a menu item, like "View Source" 
[9:28am] <andIIng> I actually do that very seldom but I wondered "if sources are just at one-click why not headers too" ?
[9:29am] <andIIng> maybe it could be just an hidden preferences when looking sources, show_headers_too true/false
[9:29am] <cl> ooh, now *that*'s an interesting idea

I don't know how feasible that idea is, or if we'd want to do it, but filing for discussion, since the guy seemed rather put off by having to register for Bugzilla and thus unlikely to file it himself.

Comment 1

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

What's the point of seeing the headers on the source request?

Comment 2

[Stuart Morgan]

I don't think we want to add extra plumbing for a feature that not only is
useful only to a tiny fraction of users, but would be very rarely used even by
the person who wants it (and for which there is, in many cases, a simple
Terminal-based work-around).

Comment 3

[Chris Lawson (gone)]

(In reply to comment #2)
> (and for which there is, in many cases, a simple
> Terminal-based work-around).

Right, the biggest advantage I could see of something like this is cases where using curl is a headache, like with the result of form submissions or where cookies get involved.

Is this something a third party could (potentially) develop an add-on for, like the LiveHTTPHeaders extension in Firefox? If so, we need to find an interested third party ;)

Comment 4

[Stuart Morgan]

Whether a third party can/will do it or not, this is not even close to being within Camino's target feature set; we should WONTFIX it.

Comment 5

[Mark Mentovai]

It would be useful to pull the headers from a very specific request that can't be duplicated with curl for whatever reason: random or otherwise variable server output, or POST requests are examples.  But still, eh.  I wouldn't fight against it if someone showed up with a patch, though.

Comment 6

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Doing it in the manner suggested by this bug's summary requires 1) we fix bug 392017 and friends and 2) we then store (cache) the headers for the life of the page so that we can show them whenever someone decides to view-source the page.

I'd really, really like a headers feature, but it's absolutely add-on land.  As long as you don't need to do an ex post facto look at headers for a specific request, I believe you can NSPR log the http headers even in a release build, so you could make the request again....