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

Do twice check on HTTP error #310

Closed
iBobik opened this issue Mar 2, 2016 · 7 comments
Closed

Do twice check on HTTP error #310

iBobik opened this issue Mar 2, 2016 · 7 comments

Comments

@iBobik
Copy link
Contributor

iBobik commented Mar 2, 2016

HTML proofer sometimes returns this error:

External link http://canikova.cz/ failed: response code 0 means something's wrong

It propably means linked website is hosted on some shitty hosting, so it sometimes not responds to request. But some websites do it often and it causes false alarm.

Feature request: If there is error on remote site, what about to try it once again a few seconds ago? If second try will be ok, there should not be error on output, so tests will pass.

@Tuckie
Copy link

Tuckie commented Mar 3, 2016

This might be more flexible with retry_attempts and retry_delay parameters.

@fulldecent
Copy link
Collaborator

Perhaps this should be implemented upstream. A ticket is open at

typhoeus/typhoeus#182

I am not sure if retry should be in scope for implementing in this project.

@gjtorikian
Copy link
Owner

I agree. This is something that Typheous will need to support first.

@iBobik
Copy link
Contributor Author

iBobik commented May 20, 2017

@gjtorikian When Typheous will start support it, will HTML proofer do it by default? If not and there will be needed some work, this issue should be left open.

@gjtorikian
Copy link
Owner

When Typheous will start support it, will HTML proofer do it by default?

In theory, yes. HTML-Proofer just blindly passes over the Typheous/Hydra config options. It doesn't do any validation there or extra checks. So if an option is made available for Typheous, passing it through should be fine.

@vsoch
Copy link

vsoch commented Mar 3, 2020

This issue is closed, but I'm hugely in support of retry parameters. Our builds are consistently failing on travis because of one spurious URL error.

@gjtorikian
Copy link
Owner

If so then the issue should be bumped on Typheous, as noted above. This gem depends on that one for external calls.

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

No branches or pull requests

5 participants