"R.Wieser" wrote:

Vanguard,

Do you know of a site where each test page returns a different status
code from the server to check which ones that Firefox doesn't show

Do you know about Google ? Guess what I found when I asked it for such a
website - at first try, and as the first result.

And Google gave you a URL to which web site to exercise all server-side
status codes for the client to record? You didn't even provide the
search criteria to prove what you found. Besides, I asked you, not
Google.

I fixated on YOUR example.

Yes, you did. You fixated on an EXAMPLE. I suggest you look up the
meaning of "example". I don't think that it means what you think it
means.

Sorry, the battery in my crystal ball is dead and no replacement
available, so I cannot see what other scenarios you might want to also
examplify.

Also, re-read the subjectline. As far as I can tell it rather clearly
indicates that that example HTTP status code is just one of many.

Since not everything can be discussed all at once, take a 404 error.
The server is supposed to still provide a document when a 404 occurs
when failing to find the intended target. The client still gets a 404
error, but is going to show the "not found" document sent by the server.
I've been bouncing around to some high-end sites trying to find one that
doesn't do a proper delivery of an info document to announce the 404
error. Since those web devs probably inately know they're supposed to
handle a 404, or because the dev tools they use automatically provide
handlers, I haven't found one that returns no document on a 404. That
is, I'm still hunting for a server that returns no document for a 404,
so the client has to present something. Still looking for a server that
doesn't return an ErrorDocument404.

I don't have a way to edit the .htaccess for someone using Apache
webserver to comment out their line for:

ErrorDocument 404 /404.html

to replace it with yet another non-existing document, or remove the 3rd
argument to prevent the server from delivering that replacement doc.
So, I need to find a site where whomever admins the web dev completely
forgot about providing an ErrorDocument, pointed to the wrong doc (which
also does not exist), or the 404.html doc doesn't yet exist. I suspect
web server already come pre-configured with the ErrorDocument redirect
along with the actual doc file to circumvent a forgetful web dev.

Know a site where they forgot to add the ErrorDocument line in
..htaccess, omitted the 3rd parameter to point at the doc file, or don't
have the doc file (so the page you couldn't find also results in not
finding the ErrorDocument)? Sorry, a Google search just returns hits on
how to properly configure the web server to present an ErrorDocument.

Update: I might've found one. I was thinking of sites that I recently
visited, or those that came to mind, and happened upon one where the
server is misconfigured. I went to https://www.uwe-sieber.de/ (where I
can get some USB tools), and entered an invalid path, like:

https://www.uwe-sieber.de/lskdjflkjs...kjflk/rko.html

Since the web server is not configured to return an ErrorDocument, the
user sees a blank document (well, actually no document). The same thing
happens in C-Edge (Chromium Edge). I don't have Chrome installed
anymore. If you use Google Chrome to that non-existing file under that
non-existing path at the use-sieber.de site, what do you see in the
document window in Chrome's chrome?

With the extension, I can see a 404 code got returned, but the server
isn't configure to present an ErrorDocument, so the client can't display
anything. If it did display something, that seems violative to the
point of the document window as it would be showing content that was NOT
delivered from the server. This does mean the typical user thinks there
was a problem connecting to the web server rather than a problem at the
web server not delivering anything to the client.

I finally found a site that does NOT return an ErrorDocument on a 404.
Sure seems inappropriate for any web browser to present a fake document
to show the error status.

You've been told how to dig into Dev Mode to see it.

Lol. I take it you have not bothered to actually read my initial post - or
what Bob posted for that matter. He quoted my initial message in full. I
suggest you (re)read the third sentence.

And as *I* mentioned, you cannot see events before you started capturing
them! That's why a refresh was needed, so during a capture you could
see the status code. Else, turn on HTTP logging to see if that gives
you status codes during your entire web browser session.

You want to look into the past, but, as you already noted, don't know
how to do that. Sorry, I don't have a time machine to lend you. Mine
is already on loan to the Avengers (Endgame). I only know how to
capture future status by doing something before they happen.

But, that particular add-on doesn't work for me. As mentioned in the
parent, due to a bug in FF v52.

Does "bug" mean the extension will not install or load? If it is a
WebExtension (WE) extension, it needs FF 57, or later. For FF 52, you
need to find a "legacy" extension that uses the old XUL/XPCOM scheme. I
forgot to account for the change in extension modeling at version 57.
FF 57 was released Nov 2017. The extension I mentioned was last updated
Mar 2018, so it was likely a WE extension, not XUL. There is a "See all
version" link on the add-on page, but the first 1.0 version was also
written in 2018, so likely it started as a WE extension.

With Firefox 52, you're stuck with XUL extensions. addons.mozilla.org
doesn't let me search by extension type, like WebExtension or XUL, and
https://www.google.com/search?q=fire...+xul+extension was
unfruitful. I'll leave that search to you to find out if there was an
old XUL extension to capture the immediate HTTP status for a document
retrieve. If you don't find one, looks like you're stuck bring up the
console window or the Network tab in Dev mod ahead of time, or using
HTTP logging.

You seem to be suggesting that I should *always* have that "Debug
Console" open, so that I can catch the HTTP status. Really ?
Running FF in permanent debug mode just to stay aware of a simple
status ? You must be joking.

Or leave the Network tab in Dev mode selected to watch for future status
on later retrieved documents. Or enable HTTP logging. You're going to
need something that stays on to capture future statuses. The extension
I gave shows the immediate or current document status, but that looks to
be unusable under version 52 of Firefox.

Is that so ? Since when ?

Dynamic documents. You said you didn't want to do a refresh to get the
console window or Network tab to show status because the page could be
different. Well, if it's a dynamic document but you disable Javascript
then you won't be retrieving the current document, either.

Sorry, but what you ask is impossible: you want events before
they were captured.

You ofcourse have no problem in quoting where I indicated that ? Good, I'll
be waiting for it.

I didn't say you said that. That was my synopsis of your goal.

And no. I asked for something that would display the HTTP status
failure codes. I made no requirements to the how of it.

Well, sure sounds like you were stating criteria in:

And there is a problem with that Digging" : if you do not already have
that "Browser Console" open with its "Net" tab activated you have to
reload the page, possibly giving you a different result ...

If that is no longer a criteria then, yes, leave the console window
open, the Network tab in Dev mode, or use HTTP logging so the program is
ready to capture those statuses.

It sure seems from your comments that you want a means of showing past
status codes without ever enabling some form of history. You want it,
but don't know how it could be done. Apparently the option to enable
history (aka logging) didn't interest you, either, since you would only
capture the HTTP activity after you enabled that function. Even if you
enable logging, it's probably going to bog down the web browser since
that file is going to get huge over time. I suppose you could schedule
an event in Task Scheduler to periodically delete the logfile, or have
it run a batch file that deletes files older than some threshold. I
only saw the about:config option to enable logging, and nothing about
setting a max size to the logfile; i.e., to trim old entries.