Hi Graham,

thank you (and Manu) for the time you spent on this issue. It is now
somewhat fixed (s.b.).

On 15 Sep., 10:17, Graham Dumpleton <[EMAIL PROTECTED]>
wrote:
> On Sep 15, 5:35 pm, Robert Waltemath <[EMAIL PROTECTED]>
> wrote:
> [...]
> > Yes, right, mod_authz_host by default denies access to the whole
> > filesystem. In this case the DocumentRoot is fake (though it exists)
> > as I don't want it to be accessible. I only want some special
> > locations like "/trac" to work. But when I access e.g.
> >  http://myserver.net/trac/roadmap
> > I get an error for /srv/test/docroot/roadmap (and some more for /srv/
> > test/docroot/chrome..., one for each request), which means that
> > somebody must have tried to access
> >  http://myserver.net/roadmap(or the filesystem location directly)
> > AND trac is working, though there is an access-denied error.
>
> > One could say that I should just ignore the error if everything is
> > working fine, but who wants strange error messages in their logs?  :)
>
> The problem is that Location overlays on top of Directory, so
> Directory checks against DocumentRoot are done first. Thus, because
> document root isn't accessible you will get these messages.

If I give the vhost no DocumentRoot, the error messages dissapear. I
probably misunderstood something in this document:
http://httpd.apache.org/docs/2.2/en/sections.html#mergin
I normally provide a fake DocumentRoot because otherwise Apache falls
back to the default one ("/htdocs" in my case) and that's not a very
controlled behaviour. Even if I provide a "default" DocumentRoot in
the main server configuration (outside the vhosts) it won't work!


> Ultimately this is because of how Location must be used when using
> mod_python to map to Trac instance. That Location overlays Directory
> likes this is always causing problems when using mod_python.

Yes, it seems to be an issue with mod_python, because it works (and in
my opinion should work) with other examples, e.g. mod_dav_svn. Do you
have a pointer to some documentation about this mod_python behaviour?


> BTW, why don't you just mount the Trac instance as the root of the web
> server if nothing outside of that path will be accessible anyway.

Just the root itself isn't accessible (though there is a redirect),
but there are more services under different locations.


> Also, if you used mod_wsgi you would not get these problems as it uses
> Alias instead of Location to map to Trac. There will be no messages
> because Alias takes precedence over Directory and DocumentRoot. If
> interested in Trac setup with mod_wsgi see:
>
>  http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac

Thank you for the pointer, maybe I try to use this in the future. I
just didn't do it by now, because of the sentence "While mod_wsgi is
very new and somewhat experimental ..." in 
http://trac.edgewall.org/wiki/TracInstall

Thank you again,
robert


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" 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/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to