| 2010-06-15 01:55:13 |
Robert Collins |
description |
We've set up a smart server instance using WSGI so that we could place access controls on the project branches. We really like to use a checkout of the server's branch to make merging into the mainline easier. Unfortunately, 'bzr co' attempts to acces .bzr/branch/branch-format instead of going through the smart server. Since we don't allow raw access to the branches, this fails. It should really be using the smart server transport. Interestingly, 'bzr branch --bind' works fine.
Sorry I can't give you a short way to reproduce this, but I'd be happy to try a patch. |
For access control, HTTP server operators would like to push all bzr content access through the smart server, but 'bzr co' and other operations may fall back to VFS from time to time. When they do, they currently make the VFS requests over plain HTTP even though a smart server is present. For consistent application of ACLs it would be better to tunnel the VFS requests via the smart server.
|
|
