2013-01-07 16:11, Alan McGinlay skrev:
Hi,

I am trying to find a good way to redirect example.com/~username to a
specific backend (which will run apache and nfs mounted home
directories) in order to keep users public_html and nfs mounts off of
our main webserver.

We also have multiple domains pointing at the same backend but I would
like the userdirs to only be available via one of them so that
example.com/~bob works but otherexample.com/~bob does not.

So far I have this:

     Service
         HeadRequire "^Host:\s*www.example.se.*"
     URL "/~*"
         BackEnd
             Address userdirhost
             Port    80
         End
         Emergency
                 Address localhost
                 Port 9090
         End
     End

Followed by:

     Service
         HeadRequire "^Host:\s*www.example.se.*"
         BackEnd
             Address standardbackend
             Port    81
         End
         Emergency
                 Address localhost
                 Port 9090
         End
     End

However, although this allows the userdir to work, it also completely
breaks the second entry..


Any advice?

Thanks,

Alan

--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.

I found the following similar question on the archives:

http://www.apsis.ch/pound/pound_list/archive/2009/2009-03/1236583386000

However it doesn't seem to work (ldd shows pound compiled against pcre libs).

with the original configuration i posted, browsing to site.com/ redirects to the userdir server and gives a 404. Browsing to site.com/~user does NOT redirect to the userdir server and gives a 404 generated on the normal webserver but if i add a trailing slash to that url then it redirects to the userdir server correctly and shows the users content..

Not sure what the heck is going on here or how to debug it :(

--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.

Reply via email to