I'm sorry for the trouble, and can understand the frustration. However this is considered working as intended. ffuf doesn't set the content type header for different payloads automatically. As there's plenty of different ones depending on the payload, this is left for the users discretion.

I personally find it much easier to work with -request and -request-proto where you would save the raw request to a file, edit the fuzz keywords in place, and pass it in by: ffuf -request saved-req.txt -request-proto https ....

I think if this is intended, it should be mentioned in README.md. Because I took a lot of hours to find out why my POST requests didn't work. Maybe just a simple example to be more clear.

Thank you.

Make sense @sangvo1991, good observation!