-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
URLs without prefix of "./" get a 404 #374
Comments
Now I don't think it even works when it does start with "./". I changed the link to http://localhost:8080/apps/web Maybe the real problem is that my links don't explicitly reference an index.html file? |
I was about to report what I think is the same problem. It was just introduced in one of the last few releases. With 3.0.3 it reports every relative link to another file in the same directory as being broken:
etc. But with 3.0.0 it reports all those links as being found. |
Greetings! Can you share a few things with me to make debugging easier?
I'm trying to reproduce this, but having a little trouble figuring out exactly what's happening :) |
Thanks! We're building HTML documentation with Sphinx, and using linkinator on Github Actions to check for broken links in each PR. Here is the section of the script that runs it.
As you can guess, the
|
If you run it against my website you will see a lot of invalid 404s reported. npx linkinator https://worldtreesoftware.com --recurse One example, it's looking for "intro" in the parent instead of relative to the current page. It should be looking here: https://worldtreesoftware.com/apps/web/harmonograph/intro |
Relative URLs without prefix of "./" get a 404. For example:
<a href="harmonograph">
in http://localhost:8080/apps/web reports this error:http://localhost:8080/apps/web
[404] http://localhost:8080/apps/harmonograph
The link works in the browser resolving to the current folder, but in linkinator it seems to be resolving to the parent folder. It should resolve to this folder instead: http://localhost:8080/apps/web/harmonograph
The text was updated successfully, but these errors were encountered: