Re: [Chicken-users] Spiffy bug with header/response code preservation in threads

[Peter Bex]

On Sun, Mar 30, 2008 at 10:25:10PM -0700, Robin Lee Powell wrote:
> 
> This one's about as annoying as the content-length bug (a lot) and
> about as difficult to work around (quite easy, actually).
> 
> Basically, if you don't explicitely clear headers after you serve a
> request, *and* the client actually uses the same connection (i.e.
> curl does this), the headers never get cleared, which leads to
> surprising behaviour, such as a normal page serving a redirect
> because the last page was a redirect.
> 
> This is also true for the response code, which is just as bad, if
> not worse.

Sorry it took a while, but I've finally got around to writing tests and
fixing both bugs.

Could you try out spiffy trunk and let me know if it works for you?  If it
does, I'll push a new release.

Cheers,
Peter
-- 
http://sjamaan.ath.cx
--
"The process of preparing programs for a digital computer
 is especially attractive, not only because it can be economically
 and scientifically rewarding, but also because it can be an aesthetic
 experience much like composing poetry or music."
                                                        -- Donald Knuth

pgpIDGAH7lWid.pgp
Description: PGP signature