Hi! I'm new to ssl and am having some problems. I'm working on an
http server; the interface is in perl and the internals are in perl and
C; the SSL module is in C.
Everything works fine except for large file uploads (using
multipart/form-data), where I lose a *variable* fraction of a percent
On Fri December 9 2011, MK wrote:
Hi! I'm new to ssl and am having some problems. I'm working on an
http server; the interface is in perl and the internals are in perl and
C; the SSL module is in C.
Everything works fine except for large file uploads (using
multipart/form-data), where I
Hi, nice code, I spot a few questionable details, but only Warn#5 might
cause missing bytes.
On 12/9/2011 1:28 PM, MK wrote:
Hi! I'm new to ssl and am having some problems. I'm working on an
http server; the interface is in perl and the internals are in perl and
C; the SSL module is in C.
On Fri, 9 Dec 2011 07:55:07 -0600
Michael S. Zick open...@morethan.org wrote:
Evidently your connection is doing a renegotiation during the
transfer. You missed:
http://stackoverflow.com/questions/3952104/how-to-handle-openssl-ssl-error-want-read-want-write-on-non-blocking-sockets
Among a
On Fri December 9 2011, MK wrote:
On Fri, 9 Dec 2011 07:55:07 -0600
Michael S. Zick open...@morethan.org wrote:
Evidently your connection is doing a renegotiation during the
transfer. You missed:
On Fri, 09 Dec 2011 15:10:47 +0100
Jakob Bohm jb-open...@wisemo.com wrote:
Hi, nice code, I spot a few questionable details, but only Warn#5
might cause missing bytes.
if (!field) return newSV(0);
Warn#1: It is probably more efficient to return PL_sv_undef, avoiding
an allocation
On Fri, 9 Dec 2011 09:08:19 -0600
Michael S. Zick open...@morethan.org wrote:
On Fri December 9 2011, MK wrote:
What makes you believe I am not handling this correctly? If the the
call returns WANT_WRITE or WANT_READ, it gets called again with
exactly the same parameters, which is exactly
