On Friday 16 September 2005 11:28, Brion Vibber wrote:
1.4.0 is ancient, buggy, and has a number of known security problems. Under no circumstances should you be running a 1.4.0 wiki in public.
Well, I know. My wiki is located in an intranet. I was originally planning to update to 1.5 soon.
Concerning $wgServer, $wgScriptPath and $wgArticlePath I have no real clue on how to change them to fix my problem.
I could set $wgServer to the reverse Proxy URL like "http://www.myproxy.com", but then I can only access my mediawiki through the proxy, but not from other interfaces.
MediaWiki is designed for internet-facing wikis which have a single well-known URL location. There is no support for changing the URL path depending on who's visiting (among other things the URLs are embedded in cached data).
Okay. What happens if MediaWiki is running behind a load-balancer? I guess that the servers at big sites like Wikipedia are not directly connected with their interfaces to the internet. They are behind load-balancers or something similar. Now, they should face a similar problem than me. If mediawiki sends a redirect with the URL of the local interface, the load-balancer must handle that. The browser will never see this IP address, but the address of the load-balancer.
However, I think I will focus now on a solution based on Apache module mod_proxy_html in order to remove absolute paths in links.
Thanks Ralf