We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The check404 function does some implicit checks (e.g. webpages with django debugging enabled) by parsing the 404 error page.
This design has the downside that it is not possible to explicitly call those checks (e.g., snallygaster -t djangodebug [host]).
snallygaster -t djangodebug [host]
One idea would be to change the code like this:
This would both allow calling those tests separately, but would not slow them down with multiple fetches if we do a full host scan.
The text was updated successfully, but these errors were encountered:
cc @hartwork
Sorry, something went wrong.
Sounds like the right direction for a start 👍
No branches or pull requests
The check404 function does some implicit checks (e.g. webpages with django debugging enabled) by parsing the 404 error page.
This design has the downside that it is not possible to explicitly call those checks (e.g.,
snallygaster -t djangodebug [host]
).One idea would be to change the code like this:
This would both allow calling those tests separately, but would not slow them down with multiple fetches if we do a full host scan.
The text was updated successfully, but these errors were encountered: