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

[Robin Lee Powell]

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.

Code and output attached.

-Robin

-- 
Lojban Reason #17: http://en.wikipedia.org/wiki/Buffalo_buffalo
Proud Supporter of the Singularity Institute - http://singinst.org/
http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/

spiffybug.scm
Description: Text document

spiffybug.out
Description: Text document