Hey zWingz, what's the use case for defining a content type if there is no content?

may want to check the RFC https://www.rfc-editor.org/rfc/rfc7231#section-4.3.3 it is accepted that a post request would at least have a body of {} if it was nothing and not just no body at all

Hey @NikoRaisanen , would love to work on this issue. Can you please assign to me?

I have the opposite problem. When I try to send a POST with no body, the request is sent with a Content-Type of application/x-www-form-urlencoded. This value is never set explicitly in my code, I don't know where it comes from. And I can't find a way to completely suppress the header. Explicitly setting it to undefined has no effect. Setting it to null or an empty string sends an empty header. Is there a way to remove it?

@tlevesque-ueat

Is there a way to remove it?

Just set Content-Type to false

Just set Content-Type to false

As far as I can tell, it does the same thing as setting it to null or an empty string (sends an empty header).
Doesn't seem to be a problem in my scenario, though, so I'll stick to that. Thanks

@tlevesque-ueat The false value completely removes the header from the set and prevents Axios from setting it in the dispatch sequence.

Yes, I realize that now. The tool I was using to inspect the request (webhook.site) was showing an empty Content-Type, but it doesn't seem to actually be present in the request. Thanks!