A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » General XP issues or comments
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

FireFox 52 not showing any failure-result codes.



 
 
Thread Tools Display Modes
  #16  
Old January 25th 21, 07:00 AM posted to microsoft.public.windowsxp.general
VanguardLH[_2_]
external usenet poster
 
Posts: 10,881
Default FireFox 52 not showing any failure-result codes.

Bob F wrote:

R.Wieser wrote:

Just now I entered an URL into FF 52 which resulted in a blank
window. Asking for the sourcecode gave me the same blank window.
Only after opening the "net" tab on the "Broser console"
(ctrl-alt-j) window and reloading I saw that I got a 410 (gone)
result.

Question : how do I get FF 52 (on XPsp3) to show "failure" (non 200)
codes ?


I just tried it on FF 84.0.2 and just got a blank (white) page.


Did you go into Developer Mode to look at the return status code under
the Network tab?

The complaint is that Firefox doesn't show the user the 410 error code
unless you dig into Dev mode. I'm trialing an add-on that shows the
status code returned by the server.

https://addons.mozilla.org/en-US/fir...p-status-code/

So far, it's worked okay. You can also click on the add-on's toolbar
icon to be taken to a httpstatuses.com web page explaining the status
code. Don't know if I'll keep it, though, unless I hit more sites where
Firefox present an empty document instead of showing error status codes.
Ads
  #17  
Old January 25th 21, 09:48 AM posted to microsoft.public.windowsxp.general
R.Wieser
external usenet poster
 
Posts: 1,302
Default FireFox 52 not showing any failure-result codes.

Bob,

I just tried it on FF 84.0.2 and just got a blank (white) page.


Yup, the same I got. But FF just shows an empty window. There is no "page".
Rightclick and select "view page source" and you will, again, see nothing
but an empty window (not even a line number).

And as mentioned in what you quoted, if you open the "Debug window",
activate the "net" tab and reload the page you can see you actually get a
410 HTTP status back - indicating a failure in accessing the requested data.

Regards,
Rudy Wieser


  #18  
Old January 25th 21, 09:52 AM posted to microsoft.public.windowsxp.general
R.Wieser
external usenet poster
 
Posts: 1,302
Default FireFox 52 not showing any failure-result codes.

Vanguard,

The complaint is that Firefox doesn't show the user the 410
error code unless you dig into Dev mode.


No, it isn't.

Quote:
Originally Posted by me
Question : how do I get FF 52 (on XPsp3) to show "failure" (non 200) codes ?
410 is just *one* of those. You're fixating on a single number.

The part of having a "complaint" (a bit overstated) about having to dig for
the HTTP status is correct though.

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 ...

I'm trialing an add-on that shows the status code returned by the server.

https://addons.mozilla.org/en-US/fir...p-status-code/


Someone elsewhere suggested the same to me. Alas, due to a bug in FF v52
"background" scripts in such add-ons cease to run when JS is disabled -
which is something I always do.

Thanks for suggesting it to some random person instead of the guy who
started the thread with the the problem though. I really appriciate it.

Regards,
Rudy Wieser



  #19  
Old January 25th 21, 10:35 AM posted to microsoft.public.windowsxp.general
VanguardLH[_2_]
external usenet poster
 
Posts: 10,881
Default FireFox 52 not showing any failure-result codes.

"R.Wieser" wrote:

Vanguard,

The complaint is that Firefox doesn't show the user the 410
error code unless you dig into Dev mode.


No, it isn't.

Quote:
Originally Posted by me
Question : how do I get FF 52 (on XPsp3) to show "failure" (non 200) codes ?

410 is just *one* of those. You're fixating on a single number.


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
(i.e., when it shows an empty document)?

I fixated on YOUR example. You want Firefox to show the status returned
by the server. You've been told how to dig into Dev Mode to see it.
You want a different way to see status, and that was provided, too, as
an add-on. That's what add-ons are for: to add or change features than
what the web browser inately provides.

The part of having a "complaint" (a bit overstated) about having to
dig for the HTTP status is correct though.

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 ...


That's how debugging works: you don't get retroactive history until
debug is enabled, and you see what happens thereafter. I haven't
bothered to see if there is an add-on that does auditing (keep a
history) of past loaded documents before debug mode was used. That
doesn't even work when compiling: you have to enable debug mode, and
then recompile. Logging starts only after you enable it. Auditing can
be quite expensive to leave on continuously, especially if you only
rarely need to visit status history.

While I was looking for an add-on to enhance Dev mode making it easier
to readily see the status code, I found Firefox has its own logging
function at about:networking#logging. Of course, history won't start
getting recorded until you enable logging. So, sites you already
visited before you enable logging won't be in the log. I haven't
bothered using the internal logging function to know if the status code
on visiting a web page gets recorded in the log. I suspect this is a
per-session setting: you load Firefox, enable logging, and then go visit
the web sites and jump around their pages. If logging didn't turn off
when you exited Firefox, the log file would become HUGE.

https://developer.mozilla.org/en-US/...g/HTTP_logging

Since env vars or command-line args can be used to start logging and
specify detail, I suppose you could create a special shortcut that loads
Firefox with logging started, so you capture the logged items into a
file anytime during that session of Firefox.

I haven't found a hindsight feature in Firefox or for an add-on that
shows auditing, history, or logs before those features were started.
How do you capture something that wasn't captured before?

https://addons.mozilla.org/en-US/fir...p-status-code/


Someone elsewhere suggested the same to me. Alas, due to a bug in FF
v52 "background" scripts in such add-ons cease to run when JS is
disabled - which is something I always do.


Then your argument about reloading the web page might change the return
status is voided. If you disable Javascript in your client for a
document that employs Javascript then you are not getting the same
document as when Javascript is enabled.

Thanks for suggesting it to some random person instead of the guy who
started the thread with the the problem though. I really appriciate
it.


Sorry, but what you ask is impossible: you want events before they were
captured. Whatever you use to see an audit, history, or log means
you're going to have to start that function and THEN watch the events.
  #20  
Old January 25th 21, 10:47 AM posted to microsoft.public.windowsxp.general
VanguardLH[_2_]
external usenet poster
 
Posts: 10,881
Default FireFox 52 not showing any failure-result codes.

"R.Wieser" wrote:

VanguardLH,

When I go there (but I'm using Firefox 84.0.2), and then
use Developer mode to look at the code for the page
under the Inspect tab, it shows:

html
...
/html


I'm afraid your FF 84 is pulling a fast one on you. Using a raw HTTP
retrieval tool shows there is no HTML content.

Why would the web browser report an error?


Perhaps because any 4xx or 5xx HTTP status indicates (a) failure ?

But if a resource is permanently removed, a 410 (Gone)
should be used instead of a 404 status.


And that is exactly what they have done (the resource is permanently
removed) and do (returning a 410 status).

IOW, the website seems to do everything by the book.

https://wiki.openstreetmap.org/wiki/Contact_channels

Other than those contact channels, I didn't see an explicit link to
report a defect in their server's behavior


There is a "report-uri" in the returned HTTP header.

Now, as we have ascertained that the website didn't do anything wrong , lets
go back and focus on getting FF 52 to display a received 4xx or 5xx HTTP
status please.


As noted in another of my replies, YOU will have to enable or initiate
auditing, logging, or history capture BEFORE whatever events you want to
capture. No way to program in hindsight, like enabling capture now to
somehow record events that happened in the past.

Maybe when computers encapsulate a quantum realm then they could do
that. I think you're too enamored with scifi, like "Avengers: Endgame".

https://www.theringer.com/movies/201...scott-aaronson

That's sci-fi. Presumably you want something doable now, but somehow
employ unfathomable science that links the web browser to past events
before they were captured to log those and bring forward the log.

Staying real for now, if you want to capture future events, like status
codes, then you'll have to enable something now to do that, but what
gets captured will only be after you start the capture.
  #21  
Old January 25th 21, 02:32 PM posted to microsoft.public.windowsxp.general
R.Wieser
external usenet poster
 
Posts: 1,302
Default FireFox 52 not showing any failure-result codes.

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.

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.

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.

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.

But a question: *How else* did you think I knew that that link I posted
returns a 410 ? Magic ?

You want a different way to see status, and that was provided, too,
as an add-on.


No, you did not. When you mentioned that add-on you where talking to
Mayayana, not me. As such I did not even see it untill now, when I went
thru all messages trying to verify your claim.

So no, you didn't.

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

That's how debugging works


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.

Alas, due to a bug in FF v52 "background" scripts in such
add-ons cease to run when JS is disabled


Then your argument about reloading the web page might change
the return status is voided.


You may want to explain that.

If you disable Javascript in your client for a document that
employs Javascript then you are not getting the same
document as when Javascript is enabled.


Is that so ? Since when ?

Also, you're now trying to shift focus to a subset ("a document that employs
Javascript") of the pages I might request/receive. If you shift focus to
some subset often enough (410 status, now JS) you will likely arrive at a
microscopic subset in which something you say is true - but has zero bearing
on my question.

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.

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

Also, why would I want an event ? Do you think that that event just grabs
the HTTP status code outof thin air ? If not, where do you think that HTTP
status code comes from ? Do you think that there perhaps is a possibility
that I also could request that data ? If not, why ? (and for the
record: no, not knowing how is not the same as it being impossible)


VanguardLH, I recognise your name as that from a long-timer and as such have
a certain respect for it. What happened to you that you post junk like
this ?

Regards,
Rudy Wieser


  #22  
Old January 27th 21, 05:04 PM posted to microsoft.public.windowsxp.general
R.Wieser
external usenet poster
 
Posts: 1,302
Default FireFox 52 not showing any failure-result codes. - solved

Hello all,

After a lot of searching and trying I was able to piece enough XUL together
to get the HTTP status and show it in the tooltip of the add-on's toolbar
icon (not intended as the end of the story, but I've got a working, albeit
minimal, product)

It also shows a flaw of the "HTTP status code" add-on : it shows only the
last HTTP status, and the 410 status of the example link I posted would be
directly overwritten by the 200 status of the succesfull retrieval of the
webpages "favicon" ...

Regards,
Rudy Wieser


  #23  
Old February 5th 21, 12:27 PM posted to microsoft.public.windowsxp.general
VanguardLH[_2_]
external usenet poster
 
Posts: 10,881
Default FireFox 52 not showing any failure-result codes.

"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.
  #24  
Old February 5th 21, 03:30 PM posted to microsoft.public.windowsxp.general
VanguardLH[_2_]
external usenet poster
 
Posts: 10,881
Default FireFox 52 not showing any failure-result codes. - solved

"R.Wieser" wrote:

After a lot of searching and trying I was able to piece enough XUL
together to get the HTTP status and show it in the tooltip of the
add-on's toolbar icon (not intended as the end of the story, but I've
got a working, albeit minimal, product)

It also shows a flaw of the "HTTP status code" add-on : it shows only
the last HTTP status, and the 410 status of the example link I posted
would be directly overwritten by the 200 status of the succesfull
retrieval of the webpages "favicon" ...


I have the HTTPS Status Code extension installed in Firefox 85.0. It
shows the 410 status. When I look under the Network tab in Dev mode,
the favicon.ico file gets retrieved, but no status is assigned to that
GET. The client requests the favicon.ico file whether it exists or not.
It wasn't a file found by navigating the web pages for the site. Since
the client initiates the file download, status could be misleading.
That a site doesn't have the file is a web site error?

When I visit:

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

which is a deliberately invalid URL (neither the path nor file exist)
where the server does not deliver an ErrorDocument for the non-existing
document, the extension shows "404" despite there is a favicon.ico file
for the client to retrieve, and that status was "200". So, the
extension still shows the 404 error despite afterward the favicon.ico
retrieve generated a 200 success.

I couldn't get the extension to surrender the 404 error for the
requested document to show blank or 200, and the extension still showed
the 410 error for the example URL you gave. Since the extension was
first released after Firefox 57 probably means the extension used the
WebExtension scheme, so I'm surprised that extension works at all under
Firefox 52 which uses the XUL scheme.

Since the HTTP Status Code extension's code is open sourced at Github
(https://github.com/amad/http-status-code), maybe that might indicate
how it works. Hmm, maybe not. When I looked there, I didn't see the
code for the actual extension. I looked in the downloaded .xpi file
where there is an index.js file. Frankly I got lost in there. Couldn't
see where the tab object had an attribute extracted to use in displaying
in the badge for the extension, unless maybe just getting the tab by its
ID also happens to get HTTP status, like the status is the default
attribute. There is a browser.tabs.query() function, but I don't see
how that got statusCode.toString() set to the HTTP status code. The
query function doesn't have a parameter to get the HTTP status. Been a
sleepless night, no coffee, so maybe I'm missing something otherwise
obvious.
  #25  
Old February 5th 21, 03:30 PM posted to microsoft.public.windowsxp.general
VanguardLH[_2_]
external usenet poster
 
Posts: 10,881
Default FireFox 52 not showing any failure-result codes.

Something else I remember to use to track status is Fiddler2. It's been
awhile since I last used it, but, I think, it changed from just an
extension to a front-end extension to control their proxy. You used the
extension to enable/disable web traffic interrogation. I suspect I quit
using Fiddler2 when Mozilla fleshed out Dev mode in Firefox. I suppose
a step up but perhaps with more complexity would be to use Wireshark.
However, you still have to enable them to monitor or record future
traffic.
  #26  
Old February 5th 21, 03:47 PM posted to microsoft.public.windowsxp.general
R.Wieser
external usenet poster
 
Posts: 1,302
Default FireFox 52 not showing any failure-result codes.

Vanguard,

And Google gave you a URL to which web site to exercise all
server-side status codes for the client to record?


Did you ask for that ? No, you didn't.

You didn't even provide the search criteria to prove what you found.


Correct. As it was /that easy & fast/ to find that website just a little
bit of effort by yourself should have given you the same answer. I'm not
your gofer you know.

Besides, I asked you, not Google.


In that case, the answer is definitily "no". What would I need such a
website for ? Its *you* who wants to go off on that tangent, not me.

The only reason I googled for it was to see if I, nonwithstanding that
whatever you where busy with would definitily /not/ answer my question,
could help you with it. When I found such a website without putting effort
into it it gave me the strong impression you had not even tried yourself.
And that I do not accept.

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.


You are the first person who claims to need a crystal ball to be able to
leaf back to previous messages and (re?)read whats already been said. It
also shows that you are rather oblivious to anything but your own ideas.

1) Go back to this threads inintial message and read the sentence after
"Question:".

2) (re?)read my message of Wed, 20 Jan 2021 22:50:16 +0100
) and try to digest last sentence there. It
was an explicit request directed at you.



Since not everything can be discussed all at once, take a 404 error.


In one word ? No.

1) I've mentioned time-and-again that its about /all/ status codes that
indicate failure.

2) I've supplied a link to a webpage that returns a 410. Which doesn't
return /anything/ in regard to content (just a header). Exactly what you
want. Yet you ignore it.

3) I've /not once/ indicated an interrest to what (HTML) contents get
returned in the case of a failure status. That consideration is yours alone.

Yet, you (still) focus on a 404 - for reasons you have not even bothered to
share - and than complain that you cannot find any webpage examples that
deliver it without content.

And I just checked : that website that "echoes" HTTP status codes ? It
doesn't return any (HTML) contents. Exactly as you want it.

So much possibilities, and than seeing you wearing horse blinders big enough
to not notice them, *even if they are pointed out to you*.

Personally I really hope you're trolling ...

Regards,
Rudy Wieser


  #27  
Old February 5th 21, 06:15 PM posted to microsoft.public.windowsxp.general
R.Wieser
external usenet poster
 
Posts: 1,302
Default FireFox 52 not showing any failure-result codes. - solved

Vanguard,

When I look under the Network tab in Dev mode, the
favicon.ico file gets retrieved, but no status is assigned
to that GET.


And what does that tell you ? And don't tell us that you think that no
status was returned. You should know better than that.

Also, I get the feeling that you are talking about the "Dev mode" context
before the last comma, but about another one after it.

It wasn't a file found by navigating the web pages for the site.


Which website are you talking about ? Do you expect me to guess ?

It wasn't a file found by navigating the web pages for the site


Which resource are you talking about ? The one of the actual request, or
the favicon ?

Since the client initiates the file download, status could
be misleading.


Yes, thats what I already said.

That a site doesn't have the file is a web site error?


Why are you asking me that question ? I cannot not change one iota to what
the *website builder* decides about which HTTP status code should be given
to which situation on his webserver.

Also, how is that relevant to my problem/question ?

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

which is a deliberately invalid URL (neither the path nor file exist)
where the server does not deliver an ErrorDocument for the non-
existing document, the extension shows "404" despite there is a
favicon.ico file for the client to retrieve, and that status was "200".
So, the extension still shows the 404 error despite afterward the
favicon.ico retrieve generated a 200 success.


Lol. You say that as if it (ignoring "success" codes) is some
mind-boggeling complex thing to accomplish. It isn't.

Since the extension was first released after Firefox 57 probably
means the extension used the WebExtension scheme, so I'm
surprised that extension works at all under Firefox 52 which
uses the XUL scheme.


You express surprise that the "HTTP status code" WebExtension works on FF
v52 but later on in the same line you tell me that it can't be working,
'cause FF v52 uses XUL. Make up your mind please.

Couldn't see where the tab object had an attribute extracted
to use in displaying in the badge for the extension


Look for "e.statusCode".

Regards,
Rudy Wieser


  #28  
Old February 7th 21, 10:19 AM posted to microsoft.public.windowsxp.general
R.Wieser
external usenet poster
 
Posts: 1,302
Default FireFox 52 not showing any failure-result codes.

Vanguard,

I see I missed some stuff :

I suggest you (re)read the third sentence.


And as *I* mentioned, you cannot see events before you started
capturing them!


I could as easily agree as disagree with that statement, depending on which
definition I pick for those "you"s in there.

In one of its definitions you have already proven it to be wrong : *I* do
not need to "capture" anything to see those status codes come by in the
"Debug console".

And in that same direction, how does your browser respond to 302 (redirect)
status codes ? How can it do that if it doesn't /already/ "capture" the
status ?

I also, in the parent message, tried to explain how such a "capturing" could
possibly not even be needed. Which you ofcourse fully ignored. :-)

But do tell (read: explain), how does that conclusion of yours have anything
to do with my request ?

You want to look into the past, but, as you already noted,
don't know how to do that.


Thats correct. Where "into the past" equates to "the just received
webpage/resource". Just like the browser does when displaying the body of
the HTTP request. And surprise, surprise, it doesn't need a time machine
or a chrystal ball to do that.

Does "bug" mean the extension will not install or load?


To create a XUL addon you will need to include a "chrome.manifest" and
"install.rdf" file.

Thats not the answer you where expecting / looking for ? But I think its
important and really needed ! :-)

Besides, re-read what I said in the parent about it. It will come to you
eventually (yes, its in there. Really).

If it is a WebExtension (WE) extension, it needs FF 57, or later.


I'm afraid your facts aren't all that what they are supposed to be ...

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.


Pardon me ? What has that "dynamic documents" got to do with the retrieval
status ? You might want to explain that.

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.


Correct. Also, I don't really want to request the same resource twice.
Especially not when they might be downloads of the latest Ubuntu DVD (to
name something).

Well, if it's a dynamic document but you disable Javascript
then you won't be retrieving the current document, either.


You might want to rephrase that, as now its bull****.

Do I need to explain it ? You're conflating the retrieval of the initial
document with what you expect to, eventualy, see in your webbrowser.

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.


I didn't ask for where I *said* that. Just where I *indicated* it such
thing. Yes, I thought about that phrasing. :-)

The problem is that *you* cannot think of any other way - be it build in
into FF and enabled by an about:config setting or possibly by retrieving the
pages current (parsed) headers and get it from there - you have concluded
that I *must* have asked for that. Newsflash : I never have. On purpose.

My *goal* was to see the HTTP headers that indicated failure in a bit easier
way than having to dive into a "Debug console" or similar. I did, on
purpose, not specify /how/. Thats all you I'm afraid.

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 ...


No, I just pointed out how your suggested "solution" could lead to an
inconsistent result. Something I didn't think I would have needed to
explain, but here we are ...

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.


So, what you suggest is that I, everytime when I open FF, either /also/ open
the "Debug console" or go somewhere to start HTTP logging ? I thought I
already made clear that isn't an option, as its cumbersome and /way/ to easy
to forget. Especially when you're in a hurry.

It sure seems from your comments that you want a means of
showing past status codes without ever enabling some form
of history.


Nope. All I wanted was to be able to see /why/ the current page would stay
blank. All else tapers off of that.

Personally I would have been quite content with a(n about:config) setting
which would just have placed the current failure status on the empty page.

Only after had to accept I would need to use a an addon and later that I
would need create my own and after having written its first version I
decided that some enhancements would be nice. Including a small history.

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


And "over time" is defined as .... what ? Minutes ? Hours ? Days ?
Weeks ? How much history would you need ?

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.


I don't know about you, but I could imagine just throwing that log file away
on every start of the 'puter or even every launch of FF. Possibly after
having run a script to extract the relevant data from it and storing it in a
roling set of files (alike daily backups).

I've been told that Linux (power) users do that all the time. :-)

Regards,
Rudy Wieser


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 10:31 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.