[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Robin Lee Powell
Subject: [Chicken-users] Spiffy bug with header/response code preservation in threads
Date: Sun, 30 Mar 2008 22:25:10 -0700
User-agent: Mutt/1.5.17+20080114 (2008-01-14)

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.


Lojban Reason #17:
Proud Supporter of the Singularity Institute - ***

Attachment: spiffybug.scm
Description: Text document

Attachment: spiffybug.out
Description: Text document

reply via email to

[Prev in Thread] Current Thread [Next in Thread]