Ports 搜索

CGI::SSI is meant to be used as an easy way to filter shtml through CGI scripts in a loose imitation of Apache's mod_include. If you're using Apache, you may want to use either mod_include or the Apache::SSI module instead of CGI::SSI. Limitations in a CGI script's knowledge of how the server behaves make some SSI directives impossible to imitate from a CGI script.

This module is a very lightweight parser of CGI forms. And it has a special feature that it will return an array if the same key is used twice in the form. You can force an array even if only one value returned to avoid complications. The hash %cgi_data will have all the form data from either a POST or GET form and will also work for "multipart/form-data" forms necessary for uploading files.

This action implements a sensible default end action, which will forward to the first available view, unless status is set to 3xx, or there is a response body. It also allows you to pass "dump_info=1" to the url in order to force a debug screen, while in debug mode. If you have more than one view, you can specify which one to use with the "default_view" config setting (see ""$c->view($name)" in "Catalyst".)

The "Catalyst::Devel" package includes a variety of modules useful for the development of Catalyst applications, but not required to run them. This is intended to make it easier to deploy Catalyst apps. The runtime parts of Catalyst are now known as "Catalyst::Runtime". "Catalyst::Devel" includes the Catalyst::Helper system, which autogenerates scripts and tests; Module::Install::Catalyst, a Module::Install extension for Catalyst; and requirements for a variety of development-related modules. The documentation remains with Catalyst::Runtime.

SpeedyCGI is a way to run CGI perl scripts persistently, which usually makes them run much more quickly. A script can be converted to SpeedyCGI by changing the interpreter line at the top of the script. After the script is initially run, instead of exiting, SpeedyCGI keeps the perl interpreter running. During subsequent runs, this interpreter is used to handle new requests instead of starting a new perl interpreter for each execution.

This action implements a sensible default end action, which will forward to the first available view, unless status is set to 3xx, or there is a response body. It also allows you to pass dump_info=1 to the url in order to force a debug screen, while in debug mode. If you have more than 1 view, you can specify which one to use with the 'view' config setting.

Many dynamic websites perform heavy processing on most pages, yet this information may rarely change from request to request. Using the PageCache plugin, you can cache the full output of different pages so they are served to your visitors as fast as possible. This method of caching is very useful for withstanding a Slashdotting, for example. This plugin requires that you also load a Cache plugin. Please see the Known Issues when choosing a cache backend.

From README: This module automatically inserts data from a previous HTML form into the HTML input and select tags. It is a subclass of HTML::Parser and uses it to parse the HTML and insert the values into the form tags. One useful application is after a user submits an HTML form without filling out required field. HTML::FillInForm can be used to redisplay the HTML form with all the form elements containing the submitted info.

This is a collection of modules that parse HTML text documents. These modules used to be part of the libwww-perl distribution, but are now unbundled in order to facilitate a separate development track. Bug reports and discussions about these modules can still be sent to the <libwww-perl@ics.uci.edu> mailing list. Remember to also take a look at the HTML-Tree module collection that create and extract information from HTML syntax trees.

HTML::Scrubber - Perl extension for scrubbing/sanitizing html. If you wanna "scrub" or "sanitize" html input in a reliable an flexible fashion, then this module is for you. When a tag is encountered, HTML::Scrubber allows/denies the tag using the explicit rule if one exists. If no explicit rule exists, Scrubber applies the default rule. If an explicit rule exists, but it's a simple rule(1), the default attribute rule is applied.