Scan freezes on File permissions. Guzzle Error

Presumably, sitename.com is the site you are scanning? Is there anything in the logs? I'd be especially interested in the stack trace. I'm guessing this might in fact be the next scan, because the file permissions do not involve an HTTP request (other than that from your browser to run the batch iteration). Just not sure which one that would be. Maybe the Headers one.

Wonder if it's the headers check.

@chucksimply if you disable that one check does it run now?

Also know of any firewall that may be blocking your site from hitting itself to check headers?

I was thinking the same thing. I had a peek at the code in the Headers scan and I believe it should pass an option to Guzzle to not throw exceptions for "error" codes (it's in the documentation, don't remember the details). Or, alternatively, catch any exceptions Guzzle might throw (but IIRC that can be a little tricky; you'd need to catch a base exception that all other exceptions derive from, for our purposes).

Lets do that

Thoughts?

Looks good. If @chucksimply could do a functional test, that would be swell.

If we need to reopen we can no problem. Lets get that 3.0.0 release out :)

Thanks all for the quick work. New release tested and works great!

Automatically closed - issue fixed for 2 weeks with no activity.