If I configure VirtualSVN to use SSL (443), then the folder-based restrictions (read/write, read, no access) set to the folders are respected. But if I configure VirtualSVN to use simple HTTP (80), all the restrictions I set to the folders are not respected anymore, so anyone is able to explore or commit every single folder.
Is this by design or a bug? I switched to HTTP because I'm using ManagedFusion's Url Rewriter and I was not able to make it work when VirtualSVN was setup to use SSL. But when I did the switch, all the privileges set to the folders stopped to work. -- You received this message because you are subscribed to the Google Groups "VisualSVN" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/visualsvn?hl=en.
