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 notice that the BodyLocation for "body" parameters adds the name of the bound parameter to the request body. e.g. [ 'raw' => 'data' ] gets posted as an 8 byte string in the request: raw=data.
Is this deliberate? I assumed that value pairs would be handled by FormParamLocation and that the "body" location would be for raw/binary data.
I'm looking to post data as the body as if I had used --data-binary from command line cURL. For example:
> POST /something.txt HTTP/1.1
> Content-Type: text/plain
> Content-Length: 18
>
> This is plain text
Looking at the Serializer it seems I can do this for xml and json locations, but not arbitrary data.
Thanks in advance for clarification on this.
The text was updated successfully, but these errors were encountered:
Hi.
I notice that the
BodyLocation
for "body" parameters adds the name of the bound parameter to the request body. e.g.[ 'raw' => 'data' ]
gets posted as an 8 byte string in the request:raw=data
.Is this deliberate? I assumed that value pairs would be handled by
FormParamLocation
and that the "body" location would be for raw/binary data.I'm looking to post data as the body as if I had used
--data-binary
from command line cURL. For example:Looking at the Serializer it seems I can do this for
xml
andjson
locations, but not arbitrary data.Thanks in advance for clarification on this.
The text was updated successfully, but these errors were encountered: