Re: [lwip-users] HTTP keep alive SSI

2019-09-06 Thread goldsi...@gmx.de
Am 06.09.2019 um 19:39 schrieb tomek wilkxt: You could use a form of HTTP chunked encoding, You could explain more precisely ? Not in detail, that would get too long here. Just google for "http chunked encoding". Basically, you don't send a content length for the whole response in advanc

Re: [lwip-users] HTTP keep alive SSI

2019-09-06 Thread tomek wilkxt
> > You could use a form of HTTP chunked encoding, > > > > > > You could explain more precisely ? > > Not in detail, that would get too long here. Just google for "http > chunked encoding". Basically, you don't send a content length for the > whole response in advance, but you encode the conten

Re: [lwip-users] HTTP keep alive SSI

2019-09-06 Thread goldsi...@gmx.de
Am 06.09.2019 um 19:05 schrieb tomek wilkxt: Hi Tomek, are you aware of email threads and that you just hijacked another thread? Never use the "reply" feature unless actually responding to a mail! ok, my mistake And please, send text-only mails when sending mails to mailing

Re: [lwip-users] HTTP keep alive SSI

2019-09-06 Thread tomek wilkxt
> Hi Tomek, > > are you aware of email threads and that you just hijacked another thread? > Never use the "reply" feature unless actually responding to a mail! > ok, my mistake > "tomek wilkxt" wrote: > > Hi > > I read this form "httpd_opts.h" file : > > " * A downside of the current SSI impleme

Re: [lwip-users] HTTP keep alive SSI

2019-09-06 Thread Simon Goldschmidt
Hi Tomek, are you aware of email threads and that you just hijacked another thread? Never use the "reply" feature unless actually responding to a mail! "tomek wilkxt" wrote: > Hi > I read this form "httpd_opts.h" file : > " * A downside of the current SSI implementation is that persistent > conn

[lwip-users] HTTP keep alive SSI

2019-09-06 Thread tomek wilkxt
Hi I read this form "httpd_opts.h" file : " * A downside of the current SSI implementation is that persistent connections * don't work, as the file length is not known in advance (and httpd currently * relies on the Content-Length header for persistent connections). * Do you have a way to solve