This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed

On 26-Oct-06, at 11:59 PM, Kjetil Kjernsmo wrote:

> On Thursday 26 October 2006 21:07, Philippe M. Chiasson wrote:
>> Terry, Jason wrote:
>>> $ENV{=91SERVER_NAME=92}

>> That wold also work.
>> But in general, I wouldn't recommend using %ENV from within mod_perl,

> Can I ask why not? I was of the same opinion, mainly because %ENV is
> populated for every request (isn't it?) and so represents an overhead,
> but then my colleagues pointed out that if it is there allready, the
> penalty has allready been taken, so why not use it?

True, _if_ it's already in %ENV, getting the information out of there =20=

is at
virtually no cost. Getting the information out using a more direct API
call also comes at virtually no cost.

Main difference IMO? It's a shorter, more direct path to ask for $r-=20

that to use %ENV.

> To which I had no
> good answer. Perhaps %ENV can be turned off entirely?

And that's exactly it. One can do

PerlOptions -SetupEnv

or switch from

SetHandler perl-script
SetHandler mod-perl

And all magical (and CGI compatible) %ENV magic will be turned off.

And then that's when some Apache::* module starts behaving strangely,
since it was relying on $ENV{SERVER_NAME}

Hope that clarifies things a bit.=

content-type: application/pgp-signature; x-mac-type=70674453;
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit

Version: GnuPG v1.4.5 (Darwin)

iD8DBQFFRZfUyzKhB4jDpaURApcrAKCRqNbBaQBFSXtj4DHF1c 0rd8cvvgCgsXgw