I made a quick fix that HTTP/1.1 requests keep the connection open even in case of error status. So currently SHTTPD keeps the connection alive for 1. static files 2. errors
i.e. for the cases where it is easy to get content-length. in all other cases connection gets closed. You may check it now with your authorization. On 18/01/2008, Hou, LiangX <[EMAIL PROTECTED]> wrote: > Sergey, > Sorry for delayed response. I think keep-alive doesn't work properly > currently. "Authorization Required" is regarded as an error but the > connection does be kept. But the following communication cannot continue > properly. It seems that data cannot be read from remote anymore. But if we > discard keep-alive this time (to add the statement "dont_close=0" in > disconnect function), it works properly. I remember it didn't work in the > former version. > > Liang > > -----Original Message----- > From: Sergey Lyubka [mailto:[EMAIL PROTECTED] > Sent: 2008年1月10日 19:05 > To: Hou, LiangX > Cc: [email protected] > Subject: Re: [shttpd-general] shttpd cannot handle "Connection: Keep-Alive" > http header properly > > Yeah. That's because SHTTPD does not honour keep-alive if it sends > error to the client. > "Authorization Required" thing is regarded as error. > Could you try it without authorization first, please, just to make sure > keep-alive works (or does not) ? > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ shttpd-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shttpd-general
