Closed ajmeese7 closed 11 months ago
This normally happens when you talk https to an http port. In this case the server closes the connection without sending any data back, thus not being valid http. Example: curl http://google.com:443
It does not make sense to continue in such a case as all requests will end up like this but I can look into making the error message more user friendly
Thanks! 🎉
Similar to #206 , I am encountering the following error:
The web server in question is returning an empty response, but is available to reach out to via
curl
:I suspect the server in question is not hosting anything on the root of the IP, but that there are hidden directories that actually contain content and will return a legitimate response, which is why I turned to
gobuster
to suss it out. Is there a way the tool could be configured to treat an empty response as a normal 404 or something to that effect, instead of assuming that there was a problem connecting to the server?