On Sun, Nov 08, 2009 at 01:45:45PM -0500, D. Richard Hipp wrote: > > On Nov 8, 2009, at 12:55 PM, Zed A. Shaw wrote: > > > > It looks like fossil doesn't get the X-Forwarded-For header when > > it's in > > CGI mode. I had to do the proxying different so that Host is set and > > nginx doesn't use an upstream. > > > I've never heard of X-Forwarded-For before. The "X-" up front > suggests that it is a non-standard extension. Is this really a > standard HTTP header that Fossil needs to understand?
Oops, sorry wrong header, I meant Host. I dug a bit further and nginx was setting the Host wrong to just 'support', which is doesn't really explain how fossil generated: support.fretwar.com/.fretwar.com for the host. I'll dig further and figure out where the short circuit is. Oh, to answer your question about X-Forwarded-For, that's actually a header used by every proxying web server to indicate the *client* IP address, for things like logging and auditing. If there's a part of fossil that need to track client access, then this is the header to look for. -- Zed A. Shaw http://zedshaw.com/ _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
