Jason Chu wrote: > "venkatbo" <[EMAIL PROTECTED]> wrote: > > I'd like to deploy lighty in a mode where the end-user > > is not expected to be very savvy in updating the > > lighttpd.conf file after installation... At packaging time, > > I wouldn't know some of the config info (such as > > "server.bind", which is the ip-addr/FQDN of the box its > > deployed on). > > > > Is there a way (without changing lighty in its present > > incarnation) to specify that info such as this is to be > > picked up via the env or command-line. > > I assume you're using something like mod_proxy with lighty... > > It automatically sets a couple of headers: X-Host and X-Forwarded-Proto > to tell you everything you need to know about the incoming request. > > We ended up creating our own BaseUrlFilter (modifying the default > CherryPy one) to read these headers and set the request.base (which is > what tg.url, HTTPREdirect, etc uses).
Ah, thanks for the tip. Added to CherryPy 3: http://www.cherrypy.org/changeset/1339. Now tools.proxy handles X-Forwarded-Host, X-Forwarded-For, X-Host, and X-Forwarded-Proto. Robert Brewer System Architect Amor Ministries [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
