Name : perl-CGI-PathInfo
| |
Version : 1.06
| Vendor : obs://build_opensuse_org/devel:languages:perl
|
Release : lp155.1.1
| Date : 2023-07-20 16:16:43
|
Group : Development/Libraries/Perl
| Source RPM : perl-CGI-PathInfo-1.06-lp155.1.1.src.rpm
|
Size : 0.02 MB
| |
Packager : https://www_suse_com/
| |
Summary : Lightweight CGI processing package for using CGI PATH_INFO as if it were[cut]
|
Description :
Provides a micro-weight equivalent to the CPAN CGI.pm module that permits the use of the CGI environment variable \'PATH_INFO\' as a functional equivalent to the GET method \'QUERY_STRING\'. This lets you use \'extra\' URL path information as CGI parameters.
For example, lets say you have a CGI script at URL http://localhost/cgi-bin/myscript
If you were to call it as:
http://localhost/cgi-bin/myscript/some-thing/another-something/
your webserver should place \'/some-thing/another-thing/\' into the PATH_INFO environment variable when your script is run. CGI::PathInfo lets you treat that information as if it were ordinary CGI form data.
An Example:
You call http://localhost/cgi-bin/myscript/some-thing/another-something/ on your webserver. \'myscript\' contains:
use strict; use CGI::PathInfo;
my $path_info = CGI::PathInfo->new; my $some = $path_info->param(\'some\'}; my $another = $path_info->param(\'another\');
At this point \'$some\' should contain the value \'thing\' and \'$another\' should contain the value \'something\'.
This is *independant* of the use of ordinary CGI parameters. It is perfectly OK to use _both_ the PATH_INFO and normal CGI parameters at the same time.
Example:
You call http://localhost/cgi-bin/myscript/some-thing/another-something/?a=b on your webserver. \'myscript\' contains:
use strict; use CGI::PathInfo; use CGI::Minimal;
my $path_info = CGI::PathInfo->new; my $some = $path_info->param(\'some\'}; my $another = $path_info->param(\'another\');
my $cgi = CGI::Minimal->new; my $a_value = $cgi->param(\'a\');
At this point \'$some\' should contain the value \'thing\', \'$another\' should contain the value \'something\'. and \'$a_value\' should contain the value \'b\'.
Rather than attempt to address every possible need of a CGI programmer, it provides the _minimum_ functions needed for CGI such as parameter decoding, URL encoding and decoding.
The parameters decoding interface is somewhat compatible with the CGI.pm module. No provision is made for generating HTTP or HTML on your behalf - you are expected to be conversant with how to put together any HTML or HTTP you need.
CGI::PathInfo is compatible with ModPerl 1 in addition to normal CGI.
|
RPM found in directory: /packages/linux-pbone/ftp5.gwdg.de/pub/opensuse/repositories/devel:/languages:/perl:/CPAN-C/15.5/noarch |