Jason,

Thank you for your response.  I agree with your idea that this symptom is
showing up due to a mal-formed URL.

> What browser are you using, and if you've tried other browsers, does the
> error occur with all of them?  In particular, I've noticed IE will try to
> fix some bad URLs, while Netscape/Mozilla won't.

This occurs with both IE and Mozilla so I don't think its anything browser
dependent.  This points back to something in the Apache/mod_scgi area.  I've
also tried quixote 0.6.1 and gotten the same results, so I'm doubting it's
quixote specific.

> What does the URL of the link you're clicking on look like?  Does it
result
> in a redirect (that may be different depending on the elapsed time)?

The URL is actually a relative link back to the root.  Using lynx to grab
the source I get:



Quixote Session Demo: Login
Welcome, test!  Thank you for logging in.
back to start



It is "back to start" that yields the bad request.  I don't
think it results in any redirects.  I have been investigating my mod_rewrite
rules for the last few hours to make sure they are not the culprit.  Even
after disabling them all, however, the symptom persists.

Also, I've noticed that what I enter as the login affects the response.
Sometimes I'll get a:
Method Not Implemented
TTP/1.1 to /index.html.en not supported.
Apache Server at  Port 80

Depending on input, the second line ranges from:
HTTP/1.1 to /index.html.en not supported.
to
1 to /index.html.en not supported.

At this point I'm eyeing the alpha version of mod_scgi as a suspect, but I'm
also open to the possibility of a misconfiguration in apache.

I've also been trying to decipher some tcpdump data for clues.  It looks
like most valid responses to a GET are of the form:

E.....@.@.'.....
...*.P..|"..(a..
P..L<...HTTP/1.1
.200.OK..Date:.S
at,.20.Dec.2003.
17

Where as the problematic response appears to launch directly into the data
without a "content type":
E..L..@.@.......
...*.P..y...(.G.
 P..P.J..