On 15/12/2009, at 22:02, Alvaro Lopez Ortega wrote: > On 15/12/2009, at 20:22, Yo'av Moshe wrote: > >> I opened a topic about this issue long ago, but it was not resolved, and all >> my last messages got no reply... I usually understand this as "sorry, can't >> help ya", but I thought I'd give it another last chance because maybe you've >> missed it since the topic started pretty long ago (Aug' 09). >> So, sorry for the double posting, this is last time I'm bringing up this to >> the ML. > > Last time I tried, I did not manage to reproduce the problem. You're right > though, I should have replied to your mail. Anyway, I'll give it another try > tomorrow and I'll let you know.
I bring good and bad news: The good news is Cherokee is working like a charm. Bad news is, either your application or CherryPy is sending a broken request. As you know each header entry should end by the \r\n (CR LF) set. Alternatively, it could end by a single \n (LF) character. However, if you take a look at this header snipped you'll see how your application is prepending an additional \r character: ========= Set-Cookie: noal-visit=66e3682d0e27823bb1c57de8a912ed0dd71245c3; Path=/\r\r\n ========= When Cherokee detects that malformed header entry, it aborts the request. And therefore, it replies a "502 Bad gateway" error. As soon as you fix the back-end, everything should start working just fine. Cheers, -- Octality http://www.octality.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
