base_url considered harmful (trac accessed via two hostnames)
|Reported by:||Owned by:||Christian Boos|
I'm running 0.10.4dev under Apache, and now that base_url seems to be becoming more a mandatory setting for various plug-ins and even the base code, my problem is becoming more severe. I run a trac that is accessed via two URLs:
(one of them is via ssh tunnel from outside, the other is the local hostname inside the firewall). The problem is there is no possible absolute-URL setting of base_url that can work here.
Currently I have it set to "/trac" (a relative URL) which works in many cases. It satisfies all the plug-ins I currently use, e.g. RevTree. But it breaks the redirects after posting changes (e.g. new tickets) which is really annoying.
Isn't there any good way to use the scheme and hostname of the current page as the scheme and hostname of the redirect? Seems to me like base_url shouldn't be needed in almost any case; I can hope anyway.
Change History (34)
comment:21 Changed 11 years ago by
|Status:||new → assigned|
comment:29 Changed 10 years ago by
|Status:||assigned → closed|