Hey, Anyone seen this behavior? Any ideas on what to check? As I said, I'm pretty sure something has changed with Cherokee between 0.99.20 to 0.99.21 that causes these "502 Bad Gateway" errors.
My server is a production server and I'm right now it's not quite working as it should... :-p Yo'av 2009/8/12 Yo'av Moshe <[email protected]> > Hey, > I updated to Cherokee 0.99.21 and then to .22 as soon as it was out, and I > love the new status page and the graphs. Congratulations! > > It seems that ever since the upgrade, I'm having various problems with > Cherokee as a Reverse Proxy. I'm using Cherokee to serve a TurboGears > application, and ever since 0.99.21 I get "502 Bad Gateway" all the time on > certain pages. Most of these pages are where my TurboGears application is > trying to redirect the browser, but I also have redirects that works. > > I'm not sure what other information to provide, but I'm also having > troubles to downgrade to 0.99.20 because my config file has 0.99.21+ > specific keys now ("ERROR: Server parser: Unknown key "collector""), so > basically my application isn't running too-good now... :( > > Please help! > > P.S. > Needless to to say, all these pages that I get "502 Bad Gateway" for are > working perfectly when not connecting through the reverse proxy. > Also, my code hasn't changed, so these 2 things make me believe something > got wrong with Cherokee... :-s > > Thanks! > > -- > Yo'av Moshe > -- Yo'av Moshe
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
