8000 mlc reports an error on a link that works in other link checkers and via the browser. · Issue #103 · becheran/mlc · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

mlc reports an error on a link that works in other link checkers and via the browser. #103

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

Open
andrewdavidmackenzie opened this issue May 23, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@andrewdavidmackenzie
Copy link

Describe the bug
mlc reports an error on a link that works in other link checkers and via the browser.

To Reproduce

  1. On my project the README.md https://github.com/andrewdavidmackenzie/pigg/blob/master/README.md
  2. mlc
  3. Error reported
The following links could not be resolved:

./README.md (4, 1) => https://repology.org/project/pigg-x86-64-unknown-linux-gnu/versions

Expected behavior
mlc passes without error.

Desktop (please complete the following information):

  • OS: macos 15.4 Apple Silicon
  • Browser: brave (chrome)
  • Version: mlc v0.21.0

Additional context
I run other link checkers in GH Actions and they pass. I wanted one to run locally in make, and mlc seemed good, but it's failing.

I tried throttling but same result.

@becheran becheran added the bug Something isn't working label May 29, 2025
@becheran
Copy link
Owner

Hm... Interesing. When I try to reach the link with curl I do get a 403 forbidden:

curl https://repology.org/project/pigg-x86-64-unknown-linux-gnu/versions
<html>
<head><title>403 Forbidden</title></head>
<body>
<center><h1>403 Forbidden</h1></center>
<hr><center>nginx</center>
</body>
</html>

What other link checkers work with this link?

@andrewdavidmackenzie
Copy link
Author

Before, I was using:

tcort/github-action-markdown-link-check@v1

I imagine it's related to the User Agent sent in the request (maybe this site tries to avoid crawlers or something?).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants
0