Re^2: Developing CGI::Application based modules outside of the default @INC

Actually if you are on a linux/unix platform, I would strongly recommend getting your @INC path from $ENV{PERL5LIB}. This way you never have to change your code and you can change libraries from development or testing or production or anywhere else simply by changing the environment variable. This works equally well for CGI based applications as it does for CLI.

Comment on Re^2: Developing CGI::Application based modules outside of the default @INC

Replies are listed 'Best First'.
Re^3: Developing CGI::Application based modules outside of the default @INC by spacebat (Beadle) on Apr 12, 2008 at 22:03 UTC
This works equally well for CGI based applications as it does for CLI. Not quite true. Public CGI should use taint mode (as does the code in the original post), which means the environment is untrusted and PERL5LIB has no effect. Environment variables not set by CGI input should be trustworthy though. Taint::Runtime can get around this, as can something like this at the start of your script: `BEGIN { if ($ENV{PERL5LIB} && $ENV{PERL5LIB} =~ /^(.*)$/) { eval "use lib (".join(',', map "'$_'", split ':', $1).");"; die $@ if $@; } }` [download] (updated to fix a typo)	[reply] [d/l]

Replies are listed 'Best First'.

Re^3: Developing CGI::Application based modules outside of the default @INC
by spacebat (Beadle) on Apr 12, 2008 at 22:03 UTC

This works equally well for CGI based applications as it does for CLI.

Not quite true. Public CGI should use taint mode (as does the code in the original post), which means the environment is untrusted and PERL5LIB has no effect. Environment variables not set by CGI input should be trustworthy though.

Taint::Runtime can get around this, as can something like this at the start of your script:

BEGIN {
    if ($ENV{PERL5LIB} && $ENV{PERL5LIB} =~ /^(.*)$/) {
        eval "use lib (".join(',', map "'$_'", split ':', $1).");";
        die $@ if $@;
    }
}
[download]

[reply]
[d/l]