Re: [fossil-users] Fossil behind reverse proxy

2010-01-30 Thread Kyle McKay
On Jan 30, 2010, at 04:00, Paul Ruizendaal wrote: > Hi Kyle, > > In the default admin setup, the logo path > needed to be fixed from '/logo' to '$baseurl/logo', but then it works > fully. I didn't need to do that. Must have been fixed in later versions of fossil. That would be a bug for the cg

Re: [fossil-users] Fossil behind reverse proxy

2010-01-30 Thread Paul Ruizendaal
Hi Kyle, Thanks for your extensive reply. I was going through the code and had stumbled upon the SCRIPT_NAME trick when your mail came in and confirmed that it was indeed possible. In the default admin setup, the logo path needed to be fixed from '/logo' to '$baseurl/logo', but then it works fully

Re: [fossil-users] Fossil behind reverse proxy

2010-01-28 Thread Kyle McKay
Paul, I'm running a fossil server behind an Apache reverse proxy quite happily. I've been meaning to add something to the wiki cookbook about this but just haven't got around to it yet. I'm doing this because: 1. I want a fossil UI to be always on and available via my web server 2. I want t

[fossil-users] Fossil behind reverse proxy

2010-01-27 Thread Paul Ruizendaal
It may be subtler and easier than I first thought: Fossil already uses the host information from the Host: header, not from its own IP. When in CGI mode, it already relocates all its absolute references to include the prefix of the cgi script location. When running as server Fossil does not do th

[fossil-users] Fossil behind reverse proxy

2010-01-27 Thread Paul Ruizendaal
I just tried to put Fossil (running as server) behind a reverse proxy (home grown, but similar to "Pound"). That doesn't work very well, because Fossil prefixes all paths in its output with a full baseURL (as seen by Fossil). The client can't use that as the reverse proxy maps an entirely differen