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 it will
treat it like a string.
Previously I had:
set content [ns_conn content -binary]
if { $content ne "" } {
lappend cmd -body $content
}
which didn't work with this code change, but sticking to bytearray aware
commands worked:
set content [ns_conn content -binary]
if { [string length $content] > 0 } {
lappend cmd -body $content
}
On 29 July 2015 at 13:55, Gustaf Neumann <neum...@wu.ac.at> wrote:
>
> hi david,
>
> i've commit a change that handles binary data different form non-binary
> data, as used on several
> places in NaviServer. With this change, the problem should be solved.
>
> all the best
> -g
>
>
------------------------------------------------------------------------------
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
