Internet Archive's ‘noscript’ version breaks without scripts

[Mæstro]

I had discovered this problem while diagnosing my (since resolved) incompatibility between the Archive and WebComponents. As noted there, this problem is distinct and merits its own thread. In a new profile, if one disables JavaScript (through javascript.enabled, without any extension), then the Archive’s scriptless home page will keep reloading itself for ever, appending &noscript=true to the address’s end each time. The same happens for the lite search. These pages load normally in my ordinary profile, where I have scripts enabled.

While the Archive is still usable in Pale Moon with scripts, this newfound glitch is too egregious to let go without comment. Whatever could be happening here?

[vannilla]

The irony is too amazing. I can't believe the scriptless page breaks when browsed with scripts disabled globally.
Anyway, while I can't look myself right now, can anybody see if the HTML contains a <noscript> tag with a redirect directive inside?

[tpcsanh]

Following TheRealMaestro's recipe I see the same: reloading itself in a reasonably clean profile with JavaScript disabled and works in my very worn profile with scripts enabled. I am on Windows 10.

vannilla ... would this be the code you are looking for:

Code: Select all

<noscript><div class="no-js-redirect-container" data-owner="nginx"><h2>Redirecting you to a lite version of archive.org...</h2></div><meta http-equiv="refresh" data-owner="nginx" content="0; url=/?noscript=true?noscript=true"></noscript>

[vannilla]

tpcsanh, that was exactly what I meant!
In particular, the <meta> tag.
It's basically generating a redirect to itself, but only when scripts are disabled, effectively generating a redirect loop.
Someone should contact the service operators and tell them to remove that redirect from the <noscript> tag and use other ways to do it, e.g. show a link to manually navigate to that page.

[adoxa]

I've sent them an email, let's see what happens.

[Xêrxe]

Tested on Librewolf and the same glitch occurs. After multiple iterations, I am left with:

https://archive.org/?noscript=true?nosc ... cript=true

and no working page whatsoever.

[adoxa]

I've sent them an email, let's see what happens.

Nothing.