Hey, thank you for checking the issue! I hope I understood your answer, since I don't know much about headers. I'll try to check what is it about CherryPy that does that.
But, Is there any way to make Cherkoee less strict about it, or maybe even put the appropriate line ends in case they aren't there? After all, It did work with Nginx and Cherokee until 0.99.21, and it does work on all browsers that I've checked, so maybe it isn't such a big deal... :( Maybe even if you could point me to the code that I can change, just so it would work for me? Last thing - I want to debug the problem myself, but no tool that I use shous any line-ending characters. I've tried firebug and curl. What do you use to see these characters? Thank you again! Yo'av 2009/12/16 Alvaro Lopez Ortega <[email protected]> > 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/ > > -- Yo'av Moshe
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
