You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i took a brief look to see if guessing content-type was provided by one the libraries already in use within ferox. Unfortunately, that functionality isn't present. I didn't immediately see any other premade options either. Pinning this for now, as it's a nice quality of life improvement, but it's a heavier lift than i'm able to do at the moment.
Hello, I'd like to discuss 2 enhancements. I've written them separated, so its easier to track. The other one is #1118
FEATURE REQUEST 1: automatic Content-Type
Is your feature request related to a problem? Please describe.
When using the
--data
flag, one must also specify the Content-Type header in the config file.Describe the solution you'd like
When using x-www-form-urlencoded, such as with
it could be nice if the tool automatically detects the encoding, and adds a header like:
Content-Type: application/x-www-form-urlencoded
As another example, when using json such as with
it could be nice if the tool automatically detects the encoding, and adds a header like:
Content-Type: application/json
Describe alternatives you've considered
I know this feature could be hard to implement, but I believe It can be simple. Basically with
Content-Type: application/x-www-form-urlencoded
Content-Type: multipart/form-data; boundary=----WebKitFormBoundaryXXX
Content-Type: application/json
you have 99% of body encodings covered.
Additional context
N/A
The text was updated successfully, but these errors were encountered: