Handle Common Gateway Interface requests and responses
https://metacpan.org/release/CGI
CGI.pm is a stable, complete and mature solution for processing and preparing
HTTP requests and responses. Major features including processing form
submissions, file uploads, reading and writing cookies, query string generation
and manipulation, and processing and preparing HTTP headers. Some HTML
generation utilities are included as well.
CGI.pm performs very well in in a vanilla CGI.pm environment and also comes
with built-in support for mod_perl and mod_perl2 as well as FastCGI.
- Devel package for openSUSE:Factory
-
2
derived packages
- Links to openSUSE:Factory / perl-CGI
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout devel:languages:perl/perl-CGI && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| CGI-4.30.tar.gz | 0000196945 192 KB | |
| _link | 0000000124 124 Bytes | |
| cpanspec.yml | 0000000669 669 Bytes | |
| perl-CGI.changes | 0000022464 21.9 KB | |
| perl-CGI.spec | 0000002776 2.71 KB |
Revision 20 (latest revision is 79)
Stephan Kulow (coolo)
accepted
request 401401
from
Stephan Kulow (coolo)
(revision 20)
- updated to 4.30
see /usr/share/doc/packages/perl-CGI/Changes
4.30 2016-06-08
[ FEATURES ]
- Add SameSite support to Cookie handling (thanks to pangyre)
[ INTERNALS ]
- The MultipartBuffer package has been renamed to CGI::MultipartBuffer.
This has been done in a way to ensure any $MultipartBuffer package
variables are still set correctly in CGI::MultipartBuffer. if you are
explicitly using MultipartBuffer in a form such as:
MultipartBuffer->new
your code will break. you should be calling:
CGI->new->new_MultipartBuffer( $boundary,$length );
to ensure the correctly package is called. if you are extending the
MultipartBuffer package though use of ISA or base (or parent) then you
will need to update your code to use CGI::MultipartBuffer
- fake using strict and warnings to appease CPANTS Kwalitee
4.28 2016-03-14
[ RELEASE NOTES ]
- please see v4.21 Changes for any potentially impacting changes
Comments 0