The Http.post operation (#57) sends the request body as-is with no Content-Type header. For JSON APIs, the server may reject the request or misinterpret the body without Content-Type: application/json.
Workaround
Most JSON APIs are lenient and will accept the body without Content-Type. For strict APIs, this is a blocker until custom headers (#351) are supported.
Possible fix
Either infer Content-Type from body content (if it starts with { or [, use application/json), or default to application/json for POST, or wait for custom headers (#351).
Related: #57 (Http effect), #351 (headers)
The
Http.postoperation (#57) sends the request body as-is with noContent-Typeheader. For JSON APIs, the server may reject the request or misinterpret the body withoutContent-Type: application/json.Workaround
Most JSON APIs are lenient and will accept the body without Content-Type. For strict APIs, this is a blocker until custom headers (#351) are supported.
Possible fix
Either infer Content-Type from body content (if it starts with
{or[, useapplication/json), or default toapplication/jsonfor POST, or wait for custom headers (#351).Related: #57 (Http effect), #351 (headers)