> I have a root page for a website that is active and
> now it consumes
> all the request for user account home dirs too. How
> can I convince
> midgard/apache to give precedence to requests for
> /~user as
> mod_userdir requests and not mod_midgard?
Haven't had the problem with userdirs, but with images
served from the file system - since I was converting
an existing site, I wanted to keep the images that
were part of the layout in the /images dir.
You can override the "activeness" of the root dir by
creating a _static_ subpage "images".
Midgard will not find a corresponding page for the
request for /images/something.jpg and will then pass
it on to the normal handling by the Apache server.
In case of a request for the directory itself
"/images" (if that makes sense), you'll have to
provide code in the page, maybe something like:
<? header("Location:
http://www.yoursite.org/images/index.html";); ?>
I suppose you don't want to create a static subpage
/~some_user for every user on your machine. But maybe
you can move your user pages to a subdir such as
/users/~some_user and then simply have this static
"/users" page?
pascal
__________________________________________________
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes
http://autos.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
