-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lennart Regebro wrote: > 2009/10/16 Tres Seaver <tsea...@palladion.com>: >> Hmmm? A TCP socket corrresponds to exactly one open file descriptor, >> which has to stick around for the response data to come back on. >> "Half-closing" it is just silly, and is only guaranteed to work where >> both ends expect to handle this case. > > Half-closing is the standard way of saying "close when you will", so > it's normal TCP-behavior. How many HTTP-servers that handle that I > don't know, but I have to agree that it's probably the right thing to > do.
Under HTTP, it doesn't make any sense: there isn't any "mixed flow" of information going on at all; everything is request-response driven. Given that varnish has as its primary mission to be an HTTP accelerator, and that the behavior is unexpected (in ten+ years of web programming, I've *never* seen this behavior before), I would say that varnish should make the "half-close" either go away (since it provides no benefit) or at least configurable (since it breaks talking to servers which don't expect the HUP). Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkrYlS0ACgkQ+gerLs4ltQ5xAQCgw/Ifz0asq2Df4gAtSZqIQ7Ha zvgAn3qXgL3tT9ynJ48rN438FUWSsONl =5YXq -----END PGP SIGNATURE----- _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )