-
-
Notifications
You must be signed in to change notification settings - Fork 200
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
failed: 0 Server returned nothing (no headers, no data) #200
Comments
I am also seeing this with TechCrunch URLs (in addition to all WordPress URLs). See https://travis-ci.org/benbalter/benbalter.github.com/builds/59152824 for an example. Perhaps Travis's IP is blacklisted? Curl or requesting the page without an agent header returns the content as expected. |
Seems not. I see HTML::Proofer.new(['http://techcrunch.com/2011/01/07/twitter-informs-users-of-doj-wikileaks-court-order-didnt-have-to/']).run
Checking 1 external link...
-
* External link http://techcrunch.com/2011/01/07/twitter-informs-users-of-doj-wikileaks-court-order-didnt-have-to/ failed: 0 Server returned nothing (no headers, no data)
RuntimeError: HTML-Proofer found 1 failure! |
The Typhoeus User Agent is being blocked: HTML::Proofer.new(['http://techcrunch.com/2011/01/07/twitter-informs-users-of-doj-wikileaks-court-order-didnt-have-to/'], :typhoeus => { :verbose => true, :headers => { 'User-Agent' => 'LOL' }}).run
Running ["ImageCheck", "LinkCheck", "ScriptCheck"] checks on ["http://techcrunch.com/2011/01/07/twitter-informs-users-of-doj-wikileaks-court-order-didnt-have-to/"] on *.html...
Checking 1 external link...
Hostname was NOT found in DNS cache
Trying 192.0.79.33...
Connected to techcrunch.com (192.0.79.33) port 80 (#0)
HEAD /2011/01/07/twitter-informs-users-of-doj-wikileaks-court-order-didnt-have-to/ HTTP/1.1
Host: techcrunch.com
Accept: */*
User-Agent: LOL
HTTP/1.1 200 OK What are the ethics involved in my changing the User-Agent to something non-static to avoid being blacklisted again? |
You too can test this with a simple
|
@gjtorikian Do you have any sense if we're being blocked by Travis or if we're being blocked by Drupal, WP, etc.? @nacin do you have any idea why |
Failing test on
|
@gjtorikian I believe the issue is someplace in Example:
Edit: My guess is this broke when WP started enforcing HTTPS, which would be a redirect to a redirect. Either way, we should properly handle contentless redirects. |
Interesting! I'll take a look. |
Some external sites are giving an error when I test from travis-ci.org:
I added them to my exclude, but I'd rather not. Any ideas as to why this happens?
The text was updated successfully, but these errors were encountered: