Skip to content
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

Fail check on non success status code #501

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

clample
Copy link
Contributor

@clample clample commented Jan 4, 2017

Currently, external links resulting in a 404 error or other non success status codes will still pass the check.

With these changes, the user is now alerted about non success status codes from external links.

@clample
Copy link
Contributor Author

clample commented Jan 10, 2017

I'm not sure if an error makes sense for all non 2** response codes. It seems like we might get non 2** response codes for pages that are still accessible from the browser. For example, https://medium.freecodecamp.com/yes-im-56-and-learning-to-code-f33abea6fd4c#.zhqs1isvb gave a 409 error when running the check tool but I was able to access this from the browser.

On the other hand, it might be better to over-report issues when looking for broken links than to let possible issues go unnoticed.

If an external link results in a non success status code (for example 404), we now alert the user with an error.
@clample clample force-pushed the link-check-failure-on-non-200 branch from 581e62d to f5c5d78 Compare January 10, 2017 01:03
@jaspervdj
Copy link
Owner

This looks good but I think that 3xx status codes should also be valid, external URLs should be free to be moved around.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants