Sol.no - 500 error

[Tomaso]

Pale Moon has a hard time loading https://sol.no/ now..
Sometimes it works, but most of the time, I get a page that shows a "500 error".

In the console:

Code: Select all

DOMException [InvalidAccessError: "A parameter or an operation is not supported by the underlying object"
code: 15
nsresult: 0x8053000f
location: https://sol.no/logan/_next/static/chunks/commons.81520572acb5d684f267.js:1]  
main-ca029925028d11ab0d2a.js:1:11552

The same issue occurs with Firefox, but Chromium always loads the page just fine.

Is this something that needs looking into, or is it just another case of Chromium allowing errors that it shouldn't?

[adesh]

This is a server programming error while handling the request and not something a browser can do anything about.

[Moonchild]

For reference, for the future, http errors are divided into several categories:
200-range: the request succeeded
300-range: some form of redirect response (including the informational redirect that a server-side resource wasn't changed)
400-range: client error (bad request, unauthorised request, 404 not found, etc.)
500-range: server error (server internal error, overloaded, etc.)

By definition, anything in the 500 range is something internal to the server.

[rereser]

edit , posted wrong info.

[Tomaso]

By definition, anything in the 500 range is something internal to the server.

Yeah, what I was wondering though, is if Pale Moon should "allow" these sort of errors, so-to-speak, and load the page regardlessly, like Chromium does.

--

page works fine with a script block from lp4.io

No.
I'm already blocking lp4.io, so their scripts has got nothing to do with the error.
Like I pointed out in my first post; sometimes Pale Moon will load the page, but most of the time, it doesn't.

[Isengrim]

Yeah, what I was wondering though, is if Pale Moon should "allow" these sort of errors, so-to-speak, and load the page regardlessly, like Chromium does.

There is no "allowing" these errors. The error means that the server messed up and the browser literally can't do anything about it. If the page fails to load, it fails to load.

[rereser]

i stand corrected about the lp4.io block.
sometimes it works and then not.
will edit my previous post.
can only add that with a full script block using noscript the page always loads.
maybe you can use this info.

[gepus]

As far as I can see in this case the server error 500 is fake message sent by the server.
With cookies blocked the server gives an error 500.
As soon as I enable cookies the site loads instantly.

[Tomaso]

As soon as I enable cookies the site loads instantly.

No, that's not it either.

The offending scripts are dynamic ones, but adding either one of these rules to my filter list fixes it (at the cost of some minor breakage):

Code: Select all

||sol.no/logan/_next/static/chunks/commons.*.js
||sol.no/logan/_next/static/runtime/main-*.js

It might not always work with an empty cache though, if sol.no is set as your start page, as some adblockers loads too slow at first launch.

[gepus]

Tested again and again. Same result for me at least.
Don't know if it is of any relevance but I'm testing in private mode browsing.

[Tomaso]

I've sent them an mail, informing them of the error.

[Tomaso]

Already got an answer from them, telling me that they've redirected my message to their webmasters.

Off-topic:

Regarding problem reporting..
A couple of days ago, I sent an e-mail to GlobalTools, informing them of a UA sniffing issue at their web sites ( https://www.globaltools.dk/ / https://www.globaltools.no/ / https://www.globaltools.se/ )
When using Pale Moon, all of their sites refused to load, showing only a blank page, forcing me to use a UA override in order to access them.
Here's the reply that I got from them (translated from Danish):

Thanks for your message.
At a point, we noticed some attack atempts from this User Agent, wherupon it was blocked.
We've now removed this blocking, and are monitoring its status.

Ain't that the damnedest thing?
I've got no idea as to what type of attacks they're refering to, but I've never heard of anyone blocking an entire web browser as a solution to such things!

[Tomaso]

The problem appears to have been fixed now! :)

[New Tobin Paradigm]

See? Sometimes it does work.

[Tomaso]

The fact that Firefox was affected too, probably helped in this case.

[New Tobin Paradigm]

The fact that Firefox was affected too, probably helped in this case.

You're not helping.