On Sat, Aug 1, 2009 at 10:56 PM, Marc<santusm...@gmail.com> wrote:
>
> Here is my VirtualHost configuration
>
> <VirtualHost *:80>
>    ServerName myproject.host.com
>    # We can't use Location / because then /login also gets sent to
> mod_python
>    <Location />
>        SetHandler mod_python
>        PythonInterpreter main_interpreter
>        PythonHandler trac.web.modpython_frontend
>        PythonOption TracEnv /var/trac/myproject/
>        PythonOption TracUriRoot /
>        SetEnv PYTHON_EGG_CACHE /var/trac/.egg-cache/
>    </Location>
>
>    <Location /login>
>        AuthType Basic
>        AuthName "Trac (Subversion) access"
>        AuthUserFile /etc/apache2/svn.passwd
>        Require valid-user
>    </Location>
> </VirtualHost>
>
> The problem is that the Login location does not work. Trac' (NOT
> mod_python), hijacks everything and sends it to itself. Even setting
> SetHandler None in <Location /login> does nothing.
>
> The famous "Authentication information not available" message appears.
> Apache never is able to handle the <Location /login>, Trac hijacks it.
>
> Has anybody ever solved this long-standing issue? It seems to be a
> problem with Trac, because other mod_python apps like Django use the
> SetHandler None solution and it works fine.
>
> Using DocumentRoot does no difference whatsoever.
>
> Thanks.

If I understand correctly, you *want* Trac to handle /login.  Trac has
a request handler for /login that handles generating the Trac cookie
if authentication information is provided by the server.  Otherwise
Apache is just authenticating /login and then doing nothing at that
location.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to