Skip to content
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

Support body data in POST requests #32

Open
fsaintjacques opened this issue Aug 23, 2016 · 4 comments
Open

Support body data in POST requests #32

fsaintjacques opened this issue Aug 23, 2016 · 4 comments
Assignees

Comments

@fsaintjacques
Copy link

fsaintjacques commented Aug 23, 2016

It is quite common to pass data via body in POST requests nowadays, having a -d flag à-la curl would be really useful :). As a remeinder, -d works in 2 ways:

  • direct mode -d'my custom embedded data'
  • file mode -d@path_where_my_data_is.json
@shekyan
Copy link
Owner

shekyan commented Aug 23, 2016

Sure, this is something to consider. Do you expect the data be slowly served as well e.g. for slow POST, or enable this for only slow read type of attacks?
I can see it be useful for slow read, where a specific body data can trigger a special handling path, but don't see a benefit of slowly serving specific data. But who knows..

@shekyan shekyan self-assigned this Aug 23, 2016
@fsaintjacques
Copy link
Author

In our specific case, we want slow read on the response body. The body of the request is used such that the server doesn't answer back a 5xx.

Specifically, we want to see how timeouts configuration in our server behaves with clients that slowly slurp response body.

@tchelidze
Copy link

Any updates ?

@joknoxy
Copy link

joknoxy commented Nov 22, 2023

I can see another practical use-case here - if the server has added a WAF mitigation that looks for signs of non-legitimate request bodies and blocking those, then this feature could be used to test around that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants