Re^3: How to parse URL in CGI.pm

Is this safe? Can I count on it to always give me the correct URI?

Its safe in the sense that it is only data.

Since REQUEST_URI is not part CGI spec, it won't be available on every server, so its better to rely on other variables (PATH_INFO/QUERY_STRING...)

Comment on Re^3: How to parse URL in CGI.pm

Replies are listed 'Best First'.
Re^4: How to parse URL in CGI.pm by asafp (Novice) on Dec 06, 2010 at 14:41 UTC
Should there be a problem using the $ENV{'QUERY_STRING'} if the program runs under mod_perl?	[reply]
Re^5: How to parse URL in CGI.pm by ikegami (Patriarch) on Dec 07, 2010 at 09:06 UTC
The environment variable is part of the CGI interface. If your script is being provided a CGI interface, it will be present. Otherwise, it won't. mod_perl doesn't necessarily present a CGI interface to your module, but it doesn't preclude it either.	[reply]
Re^6: How to parse URL in CGI.pm by Anonymous Monk on Dec 07, 2010 at 09:16 UTC
mod_perl has option to turn that on called SetupEnv, or you can switch to CGI::PSGI and your gain easy portability between many different servers with backends like Plack::Handler::Apache2	[reply]
Re^6: How to parse URL in CGI.pm by asafp (Novice) on Dec 07, 2010 at 09:49 UTC
What if the call is POST? It seems that the ENV is empty	[reply]
Re^7: How to parse URL in CGI.pm by Anonymous Monk on Dec 07, 2010 at 13:58 UTC
Re^8: How to parse URL in CGI.pm by asafp (Novice) on Dec 07, 2010 at 15:28 UTC
Some notes below your chosen depth have not been shown here