Reverse proxy does not work with chrooting

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Configure virtual server to use reverse proxy
2. Enable chrooting and adapt all document roots

What is the expected output? What do you see instead?
Chrooting should have no impact on reverse proxy, but although static
content is served correctly the connection to Information Source gets
broken (not unavailable) immediately

What version of the product are you using? On what operating system?
Cherokee 0.11.1 on FreeBSD amd64

Original issue reported on code.google.com by type...@gmail.com on 1 Dec 2008 at 1:01

[GoogleCodeExporter]

r2513 should ease the problem a little bit.

Actually, the problem is unrelated to the proxy. The issue is that, after 
setting the chroot, a few validations fail 
but the user doesn't get a notification.

I'll check whether there is something else we could do to fix this issue.

Original comment by alobbs on 1 Dec 2008 at 12:23

• Changed state: Accepted
• Added labels: Component-Admin, OpSys-All, Type-Defect, Usability

[GoogleCodeExporter]

r2515 has fixed another related bug. Cherokee-admin wasn't taking in account 
that the log files are opened 
before the server is actually jailed.

Thanks for reporting. :-)

Original comment by alobbs on 1 Dec 2008 at 12:45

• Changed state: Fixed