smart servers requests contain embedded paths which are host relative as
the client saw it - e.g. /bzr/repo/branch
but within apache this will often be mapped to something
like /var/repos/repo/branch and thus the wsgi chroot is setup:
root=/var/repos
prefix=/bzr/
this gives us a chroot on /var/repos
however, when we parse a request from the client we get a path
of /bzr/repo/branch - giving us a local path
of /var/repos/bzr/repo/branch which clearly does not exist.
I propose that we add a convert-from-client-path call in the Request
object, to be used by anything that accepts a path from the client. It
will need the externally mapped address given to it which corresponds to
the root of the chroot (e.g. prefix above).
This makes smart server configuration appear very very hard when in fact
its a bug on our end.
affects /products/bzr
importance critical
status triaged
--
GPG key available at: <http://www.robertcollins.net/keys.txt>.
The associated branch seems to have some fixes for this. And only the last revision isn't merged.
Does that mean there is a Fix Committed, and we just need to review it? Or did it get put to the side for other fixes?