Hi Mansur,
> I've just tested app/main.l + httpGate with fresh development release, it
> works fine.
Again, many thanks for the help!
> My patches to httpGate and ssl:
> ...
> +#include
> ...
> +#include
OK. As these are just additional include files, I've also added them to
the release (sa
Hi Alex,
I've just tested app/main.l + httpGate with fresh development release, it works
fine.
My patches to httpGate and ssl:
# diff -u httpGate.c.orig httpGate.c
--- httpGate.c.orig 2012-03-20 12:46:41.0 +0600
+++ httpGate.c 2013-01-27 22:16:09.0 +0600
@@ -2,6 +2,7 @@
* (
Hi Mansur,
> Below is link to httpGate trace (it seems there is no strace in
> FreeBSD, so I used "truss"):
> http://pastebin.com/gs3t7aDL
> or should I include trace log directly into the message?
No, that's fine. I've downloaded it. Thanks!
Looking at the output
4.13311: read(4,"GET / HT
Hi Alex,
Below is link to httpGate trace (it seems there is no strace in FreeBSD,
so I used "truss"):
http://pastebin.com/gs3t7aDL
or should I include trace log directly into the message?
Best regards,
Mansur
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Hi Mansur,
> > But your description seems to refer to the _sending_ side of httpGate.
> Right.
Still, if the _receiving_ side of httpGate doesn't get complete data,
the sending side will also fail. This was the issue with the fix from
March.
> > As I understand it, 'line' should not be concerne
Hi Mansur,
> Maybe it's possible to use SO_RCVLOWAT/SO_SNDLOWAT socket options?
As far as I understand it, this should not be necessary (see below).
> Or maybe server side should do some "reassembly" (with a little
> timeouts to prevent DoS attacks) to get whole line of the request
Yes, this
Hi Mansur,
thanks for the bug report!
First of all, I'd like to ask you which version of 'httpGate' you are
using. Is it the latest one, with the source date "20mar12" (i.e.
picoLisp-3.1.0 or newer)?
> My little investigation shows, that httpGate (or TCP stack?) sends
> "GET /" in first TCP pac
