I currently use mod_python to manage permissions for a svn repository. The key part of my apache2 config looks like this:
PythonAccessHandler MyProject.svn_authz::access PythonAuthenHandler MyProject.auth::authenticate PythonAuthzHandler MyProject.svn_authz::authorize I have made attempts to replace this with mod_wsgi, like this: WSGIAccessScript /usr/local/myproject/auth.wsgi WSGIAuthUserScript /usr/local/myproject/auth.wsgi In general, this works. I can allow control to the repository by user or allow anonymous access, but unfortunately I want to be able to allow some parts of the repo to be public and grant permissions by path. Even though the access_log looks the same between mod_python and mod_wsgi, in mod_python the request object had access to path_info, which would contain the path to the file being accessed. With mod_wsgi I seem to only have access to the environment variables, with only REQUEST_METHOD and REQUEST_URI being potentially useful. Through inspection I see REQUEST_URI first contains the requested path, like when doing a checkout. Each subsequent request in the same checkout action only has /svn/!svn/vcc/default or similar URIs, which is what I see in the access_log both with mod_python and mod_wsgi. For some reason the path_info element in mod_python always had some flavor of the filename. Without being able to know the path in mod_wsgi, I'm not sure how I can use WSGIAccessScript and WSGIAuthUserScript to manage fine-grained permissions in svn. Any assistance on this topic would be greatly appreciated. Thanks, Brian -- You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi?hl=en.
