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
CI check - check external link for validity #17
Comments
100% absolutely :). I should have given more background about how this is handled with Sphinx - they have a separate "command" for it -
flex.symfony.com is a 405 - that makes me wonder if your CURL code is making something other than a GET request. I think it's ok to bring in Guzzle or some other library to do this code - it would only be a
Yea, I wonder how something like |
i'm not sure, but i think the parsers automatically converts urls into links, perhaps with a regex... example: |
closing this one in favor of |
this issue refers to the 2 of issue #10
@weaverryan Don't you think this will slow down a lot the process ? BTW, shouldn't it be the core parser that have to do this task ?
i've made some tests:
Without link status code check, execution time = 37s
With link status code check, execution time = 643s
Another thing, here is the list of all urls with a bad status code:
some of them are a bit confusing, because i don't get the same result when i'm visiting the website via my browser (ex: https://flex.symfony.com or http://redis.io/).
Some other are meant not to work (ex: http://localhost:8000/product or http://localhost:8000/lucky/number)
Here is the code i'm using to test that:
The text was updated successfully, but these errors were encountered: