On Wed, 06 Sep 2006 13:15:28 -0700 "venkatbo" <[EMAIL PROTECTED]> wrote:
> > Hi folks, > > I asked this question in the lighty forum, but to no > avail... Asking here, assuming someone may have > encountered the following scenario: > > 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. > > Thanks, > /venkat 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). Is that what you're looking for? Jason -- Two years ago, I generated a gpg key that expired August 24, 2006 (686FD13C). I've now generated a new one (C7EFE9F4).
signature.asc
Description: PGP signature
