-
Notifications
You must be signed in to change notification settings - Fork 111
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
Request feature - Response timeout #103
Comments
Thanks for the feedback! We've raised this as a feature request to be discussed further. |
No, this feature is not about the time it takes to make a request (as explain in #32 ). This enhancement is to provide a boolean to know when a request raises the TimeoutException or not. Use case:
Who could I know my rule successfully works? This is not the same usage than #32, which expected to test sql time based injection. |
I'll check with the team exactly which scenarios the feature request here would cover. For example, whether it will cover cases where there is no response from the server as well as delayed responses. I'll be in touch soon with an update. |
Hi I've checked with the team this morning, and we do have both scenarios covered in the feature requests we have created for further discussion and are monitoring here. I'll leave this open for now to make it clearer that both enhancements have been logged. |
Thank you, Waiting to see the new feature to tell you if it covers this usage. |
Hi PortSwigger team,
I propose the add a response's keyword:
timeout
as boolean value to know when the request didn't get a respond from the server for vulns like DOS.Thank you.
The text was updated successfully, but these errors were encountered: