HTTP request body should not be URL encoded
Closed this issue · 1 comments
dzieciou commented
For the following HTTP Request:
POST https://iamakamai.sqaextranet.akamai.com/ids-sso-config/restricted/idp/reminders http/1.1
Content-Type: application/x-www-form-urlencoded
INFO: Content-Length: 54
when=2017-09-26T14%3A20%3A19.425%2B02%3A00&force=false
Ok2Curl logs invalid curl command:
Ok2Curl: curl -X POST -H "Content-Type:application/x-www-form-urlencoded" -H "Content-Length:54" -H "Host:" -H "Accept-Encoding:gzip" -H "User-Agent:okhttp/3.8.0" -d 'when=2017-09-26T14%3A17%3A57.823%2B02%3A00&force=false' https://server.com/reminders
It is invalid because the HTTP request body under "-d" is already URL encoded. It should not be, because curl will encode it anyway.
mrmike commented
I've decided to not support this kind of feature right now.
Thanks