BlogSphere - Response: Sorry, this is a duplicate of NOSS-68VPHE
Sorry, didn't spot that one before I posted this.
However, using the config still seems like a good idea to me. It avoids the need to mess with Host headers in any way.
Here's my configuration, in which Host headers cause problems.
I have two servers, "intranet" and "notes". The notes server runs a couple of virtual hosts, one of which happens to be called "notes".
The "intranet" server runs a raft of stuff, so uses Apache mod_proxy to put the blog in the middle of it all. Because the notes server has virtual hosts on it, Apache *has* to specify the Host header in the requests it makes to the notes server (otherwise how would Domino know what pages to return!?). This is achieved with the ProxyPassReverse config option in apache's config.
So a user connects to "intranet/blogsphere.nsf". The intranet server then makes a fully formed request to "notes/blogsphere.nsf". Currently, that returns, crafting the HTML base as "notes/blogsphere.nsf". Therefore, all relative links on the page now directly reference "notes", when they should of course reference "intranet".
Incidentally, without virtual hosts on the notes server, Apache doesn't need to send host headers (so no need for ProxyPassReverse), so the blogsphere code works as at should (ie. it returns "intranet" in this example). Once you use virtual hosts, you have to specify which virtual host Apache should be talking to, after which blogsphere's URL crafting breaks.
Given that there is a configuration option for the base url of the blog, it would make sense to use it for this. It gives the admin complete flexibility (even allowing "intranet/blog" to return "notes/openntf/blogsphere.nsf", for example - ie. way more complex than my current scenario).
Well, that's my 2 pence worth on the subject - your mileage may vary ;-)
Documents