Closed SirWumpus closed 3 months ago
Thank you @SirWumpus for reporting this!
How did you generate that list?
I installed the Firefox add-on Simple Link Checker; then looked at the console as tool lists everything there (see aobve). Using this tool it should be possible to check other pages too.
I use the Firefox web browser, installed Simple Link Checker; clicked on the Link Checker
add-on icon generates the summary; then CTRL+SHIFT+I
to get the Web Dev tools; click on Console
- the list of redirect/broken links appears there. Right click to copy all messages
to move them to a bug report or editor.
We were unable to reproduce any of your reported link errors using Firefox 128.0.3 (64-bit), @SirWumpus .
The link https://submit.ioccc.org/ is correctly parsed by Firefox, but as that site is not yet ready (the contest is not open and the DNS for submit.ioccc.org
has not been established), that link will fail aa intended.
As we could not find a link (excluding those rate links that are not ready for access) in which Firefox 128.0.2 (64-bit) failed to load.
Quick how-to video to check links... https://github.com/user-attachments/assets/0b3b587b-0678-4631-accf-371998742ada
Nice video, but if those links are accessible by the Firefox browser: why bother?
Perhaps the link checking tool is flawed because certainly the latest Firefox browser is able to access links just fine.
Unless we are missing something, why shouldn't we close this issue as "not a bug", especially since the Firefox browser is able to view links that are designed to be accessible?
Well I think the redirect links are less important, but the four 400 class should be accounted for. Do they fail because that page isn't ready (ie. the submit URL) or truly inaccessible:
403 : https://validator.w3.org/nu/?doc=https%3A%2F%2Fioccc-src.github.io%2Ftemp-test-ioccc%2Ffaq.html redirectCheck.js:232:29
404 : https://ioccc-src.github.io/temp-test-ioccc/.top redirectCheck.js:232:29
400 : https://submit.ioccc.org/
404 : https://github.com/xexyl/winner redirectCheck.js:232:29
If these are accounted for and acceptable, then yes close this issue.
Nice video, ...
Some times you just have show what's happening vs trying to explain it.
Well I think the redirect links are less important, but the four 400 class should be accounted for. Do they fail because that page isn't ready (ie. the submit URL) or truly inaccessible:
403 : https://validator.w3.org/nu/?doc=https%3A%2F%2Fioccc-src.github.io%2Ftemp-test-ioccc%2Ffaq.html redirectCheck.js:232:29
The people who run the HTML validator appears to want to restrict the use of their tool to "humans in front of a web browser". We guess they do this in order to reduce server load. Whatever the reason, a tool such as a link checker will see an automatic link checker as a "bot" and will return an error.
Good link checkers, for reasons such as the above as well as other reasons, use a configuration system to allow one to bypass checking problematic links such as HTML validator.
404 : https://ioccc-src.github.io/temp-test-ioccc/.top redirectCheck.js:232:29
The "empty #" is assigned to be the top of an HTML file. Thus, something such as:
[top](#)
always works (very old browsers and buggy browsers not withstanding) and is always a valid link to the top of the current HTML page.
Good link checkers understand that "empty #" is always a valid link.
The submit.ioccc.org
hostname has not yet been registered in the IOCCC DNS. We plan to have, while the IOCCC is closed, for any access to anything under submit.ioccc.org
to land on a "the IOCCC is closed" page. Due to costs, we will NOT have a submit.ioccc.org
running unless the contest is pending or open.
Good link checkers, for reasons such as the above as well as other reasons, use a configuration system to allow one to bypass checking problematic links such any URL related to a site such as submit.ioccc.org
that is not yet setup.
404 : https://github.com/xexyl/winner redirectCheck.js:232:29
There is no such link / URL or even a string that contains "/xexrl
", let alone that URL.
We suspect that the link checker has a bug.
redirect ...
Redirects are not a problem. Technically when a named link such as https://example.com/foo.html#something" is accessed the
foo.htmlis accessed, the browser scans for the first "
#something`" and then jumps there. That the link checker would declare links of that form to be a redirect either is being very pedantic or has a bug. :-)
Now the way that GitHub might profess links may involve redirection in some cases. That cannot be helped. Nevertheless it is not a bug. Someone who might be trying to do so-called "search engine optimization" night care that a link automatically redirects. We are not interested in "search engine optimization" of that type. Redirects that are not automatic are a problem: only redirects that force the user to click a new link. Fortunately such "force the user to click a new link: is not happening with GitHub.
If these are accounted for and acceptable, then yes close this issue.
Thank you, @SirWumpus, we will now close this issue.
404 : https://github.com/xexyl/winner redirectCheck.js:232:29
Obviously this is a link (albeit one that is broken) to my fork of the winner repo. I can't imagine how that would have slipped through but if it did I would have to put the responsibility squarely on me. But I don't know how that would have happened either.
Bizarre. I wonder where that came from (disclaimer: have distance glasses on not reading glasses and I just saw it because we all see and hear our names out of everything else).
I will have to look at this tomorrow. I haven't used that fork in some years now since I strictly work on this one.
We suggest, however, that you might want to look for a even better link checking tool for your future projects.
List of borken and redirected link for Rules and Guidelines.
Rules
Guidelines
I installed the Firefox add-on Simple Link Checker; then looked at the console as tool lists everything there (see aobve). Using this tool it should be possible to check other pages too.