Hi David,
The implicit type conversion on the variables are a pain, but there are
already a couple
of places where this happens. Using always the Tcl_GetByteArrayFromObj
can lead
to encoding problems. One has actually the binary/non-binary problem and the
encoding problem.
I have developed a
Thanks Gustaf - I have just tried these changes and it appear to work just
fine.
I just have to be careful when handling the binary content to pass to the
-body option, if I inadvertently force an internal string representation to
be generated then if will be corrupted by ns_ssl in transit since i
Am 29.07.15 um 13:44 schrieb David Osborne:
> I found a commit for aolserver which makes the change to ns_http which
> I think I am looking for which treats the data referenced by bodyPtr
> as a byte array when appending it to the request in httpPtr->ds
> Would there be any consequences of st
Hi,
I found a commit for aolserver which makes the change to ns_http which I
think I am looking for which treats the data referenced by bodyPtr as a
byte array when appending it to the request in httpPtr->ds.
This stops invalid utf-8 bytes being transformed as when using
Tcl_GetStringFromObj which
Question - do ns_http / ns_ssl support raw binary data being passed in via
the -body argument?
*ns_http queue* ?*-method M*? ?*-headers S*? ?*-body B*? ?*-timeout T*?
*url*
*-body* body is the value which will be sent as the HTTP request body.
I'm coming across this receiving a multipart/form-dat
