Sorry for the double posting, but I found out that the link - /admin/articles_manager/9, while working on my server and not when proxied by Cherokee, actually redirects to articles/new_embed/9 which does working when proxied by Cherokee.
Maybe Cherokee gets confused because of the redirect? Yo'av 2009/12/11 Yo'av Moshe <[email protected]> > Okay, since there was no response I'm taking it a bit further. > This should be more then enough. > > I opened up my source @ maagal.dontexist.org:40 . You can click the link > and see that the website is up. > > This is how to reproduce the bug: > > - Create an information source for my server (remote host). > - Create a new virtual server with an "HTTP Reverse Proxy" handler for > my server. > - Make sure you check "Preserve Host Header". > - Save and gracefully restart Cherokee. > - Point your browser to your virtual server and follow these steps: > 1. Go to /admin/ > 2. It will ask you to log in, use "admin" and "1234". > 3. Go to /admin/articles_manager/9. > 4. You'll get 502 error from cherokee. > 5. Try it on my server, and see that it's working. > - If you want, check the same with Cherokee 0.99.20 and see that it's > working. > > Please, Alvaro, take a look at it when you can. I really can't think of any > other tools I can give you to diagnose this bug. > > Thank you. > Yo'av > > 2009/12/9 Yo'av Moshe <[email protected]> > > I'm sorry, but I just have to get this resolved... >> >> Just tried 0.99.31 and still the same. >> >> So now I have compiled cherokee with trace support, and I'm attaching the >> relevant portion of the log. >> >> Scenario is this: >> >> 1. Cherokee is up (port 80), backend server is up (port 8100). >> 2. I pointed my browser to some.url.org/login and logged in >> successfully (POST) >> 3. Moved to some.url.org/panel, and get the admin panel as I should >> (GET). >> 4. Clicked on the "Photos Panel", which is at /panel/photos/9, and got >> 502 error (GET). >> >> Same scenario is working just fine when connecting directly to backend >> system. >> >> Please, help! >> If there's anything else I can do other from this log I'll be more then >> glad to create it, just tell me what log you need... >> >> Let's get this issue fixed! >> >> Thank you. >> Yo'av >> >> 2009/10/19 Yo'av Moshe <[email protected]> >> >> Not really, since I'm can't understand why some pages work and other >>> don't. >>> >>> I can setup one of my backend servers to run on a public port - this way >>> maybe you could try to reverse proxy it. I'll tell what pages break. >>> >>> Is it okay? >>> I can also generate all sorts of logs if it will help, just say what >>> to... >>> >>> Yo'av >>> >>> 2009/10/14 Alvaro Lopez Ortega <[email protected]> >>> >>> On 14/10/2009, at 19:19, Yo'av Moshe wrote: >>>> >>>> I would love to supply any additional information about my setup. >>>>> >>>> >>>> Ok, let's try to refocus this whole issue. >>>> Do you know how could I reproduce the issue locally? That'd be enough >>>> for me to debug the problem. >>>> >>>> -- >>>> Octality >>>> http://www.octality.com/ >>>> >>>> >>> >>> -- >>> Yo'av Moshe >>> >> >> >> -- >> Yo'av Moshe >> > > > -- > Yo'av Moshe > -- Yo'av Moshe
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
