On Sun, Oct 3, 2010 at 8:08 PM, Christopher Dodunski <[email protected]> wrote: > Hi Dave, > > Thank you, I appreciate your help. I'll persevere with getting Roller > working correctly with root context but, ideally, it would be better not > to have web applications require root context. It isn't always possible > to grant it.
Roller does not require the root context, but I've only tried the multi-domain feature at the root context. > Having said that, it seems that my particular problem has more to do with > proxying. I think the ProxyPassReverse directive is inserting > "/roller/christopher" into URLs contained in HTTP headers. If true, then > this is of interest to you. As I expect many Tomcat containers are > operating behind Apache HTTP (proxy) servers. This becomes an issue with > Roller multi-domaining. Yes, I agree this is a common setup. My question is how does the proxy know about '/roller'? It seem like that is part of the problem and what you want is for the proxy to only insert '/christopher'. > How does Roller enquire the hostname when rendering these URLs? From the > header of the incoming HTTP request perhaps? Roller then responds with > the associated blog/handle as defined in roller-custom.properties? Normally, Roller will determine the URL to use in responses based on the URL used in requests. In cases where that will not work, you can specify the absolute URL of a site via the Server Admin page. - Dave
