Re: Release date for Privoxy 3.0.20 beta
Fabian Keil <[email protected]>
| Newsgroups | gmane.comp.web.privoxy.devel |
|---|---|
| Message-ID | <[email protected]> |
Fabian Keil <[email protected]> wrote: > Lee <[email protected]> wrote: > > I still see the "client side of the connection got closed" msg > > occasionally, but it doesn't seem to be causing any problems and every > > one I've checked has a long time between the last request & the > > connection being closed - for example: > > > > 2013-01-03 21:04:08.500 00000cf8 Request: > > http://i1.blogs.msdn.com/themes/wireframe/Images/Weblogs/icon-rss.gif > > 2013-01-03 21:28:37.022 00000cf8 Error: The client side of the > > connection on socket 1736 got closed without sending a complete > > request line. > > One the one hand it would be interesting to know if the client sent > any data at all for the request or how long the client connection was > open, but in general this situation doesn't necessarily imply a bug > in Privoxy (or the client) so as long as it doesn't affect the user > experience we can probably ignore it. > > I also seem to get a couple of them myself every now and then: > > fk@r500 ~/git/privoxy $grep "client side" /usr/jails/privoxy-jail/var/log/privoxy/privoxy.log > 2013-01-02 19:02:55.744 801c09c00 Connect: The client side of the connection on socket 7 got closed without sending a complete request line. > 2013-01-02 19:03:14.612 801c07c00 Connect: The client side of the connection on socket 7 got closed without sending a complete request line. > 2013-01-02 19:03:33.829 801c08c00 Connect: The client side of the connection on socket 7 got closed without sending a complete request line. > 2013-01-02 19:04:22.216 801c07800 Connect: The client side of the connection on socket 15 got closed without sending a complete request line. > 2013-01-03 11:57:25.847 801c09000 Connect: The client side of the connection on socket 7 got closed without sending a complete request line. > 2013-01-03 11:57:38.303 801c09800 Connect: The client side of the connection on socket 7 got closed without sending a complete request line. > 2013-01-03 11:57:56.839 801c09400 Connect: The client side of the connection on socket 7 got closed without sending a complete request line. > 2013-01-03 13:30:45.639 801c08000 Connect: The client side of the connection on socket 9 got closed without sending a complete request line. > 2013-01-03 13:40:03.948 801c07400 Connect: The client side of the connection on socket 6 got closed without sending a complete request line. > 2013-01-03 22:14:57.384 801c08000 Connect: The client side of the connection on socket 3 got closed without sending a complete request line. > > It's interesting that the socket number distribution seems to be > highly uneven, so it might be the result of a some kind of connection > management done by Firefox. > > For example optimistically sending "GET http://" and keeping the > connection idle until a new request has to be made and the complete > URL is known could cause this, although this seems like a somewhat > ridiculous performance optimisation. > > I'll try to look into this before the release. I looked into it and on my system (after temporarily disabling FEATURE_ACCEPT_FILTER) the client side is always closed ~5 seconds after the connection arrived and no data is sent at all. This seems to confirm that it's a Firefox optimisation to keep an open connection around just in case a new request needs it. The ridiculous additional optimisation mentioned above doesn't seem to be implemented (yet), though. Fabian ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_123012 _______________________________________________ Ijbswa-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ijbswa-developers
signature.asc
(application/pgp-signature, 834 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBCAAGBQJQ+/V7AAoJEGkYIpGLojccwS8P/i6mGjC489Pw/5OfUgUdO0hg lpp7k7/MDEEDvxs2wdzMlAZ7D4NMRQRdJojnXNVa7rBsY17fGNm71nbjb+6EYLqL k64ytxRtL7QVSFyVtxjKN9ajiGa5R75rLLINJ+5doVLCEKKG4TYxDf1hTTCquQNL 68MADYeHSEefKz6bNZVmw1vVmVa3zJDb3ecN+5SjfvZlVrB7oBz+a000H5XNd4bs MZU3pJHzmTk1cSTYHjMK8uBSDZENeSXw3vcC7GQulZ3L14XXdXi8XWtkcNJ09aeR sTf/t03ALzC77B1+k4JA4R/ZE14jExcwHKkTEJhDT0qLx5ZKRkBwTvIMdcKFcm59 gF2yhPYLNnXgIg7apVPxIXBUYDGatCBQ5VlKMm1pBD3sTLYQrWHbt4EYOntAGAVI i5VldnIcjJFwSgaqVkZaBwQ6CULfUxkkN/TtrAoMKx1mbbUVyqqRZvftNhO9CZ0K WvhXyzX1ghyz0TuqVKLSgpW9j1WvavETqpgCbgNkK0q4EryMDPU8AhP+vCntzvGp T300G7VtP2BvsynsZE3z59H87FKjzGBWbmHSDp55izp5UZ36ghbS7rIuDQSbIT2S wWHO8amoLoiWMVzdTRgp1ZlV/lvOmb7fPjR3//p0fBcStZW6e2cAfkJvr+7hRn/x wdpzIfFiUUhDBt6Xz/uN =Bng4 -----END PGP SIGNATURE-----