.\" Automatically generated by Pod::Man 4.14 (Pod::Simple 3.40)
.\"
.\" Standard preamble:
.\" ========================================================================
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Vb \" Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \" End verbatim text
.ft R
.fi
..
.\" Set up some character translations and predefined strings.  \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote.  \*(C+ will
.\" give a nicer C++.  Capital omega is used to do unbreakable dashes and
.\" therefore won't be available.  \*(C` and \*(C' expand to `' in nroff,
.\" nothing in troff, for use with C<>.
.tr \(*W-
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
.ie n \{\
.    ds -- \(*W-
.    ds PI pi
.    if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
.    if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\"  diablo 12 pitch
.    ds L" ""
.    ds R" ""
.    ds C` ""
.    ds C' ""
'br\}
.el\{\
.    ds -- \|\(em\|
.    ds PI \(*p
.    ds L" ``
.    ds R" ''
.    ds C`
.    ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\"
.\" If the F register is >0, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
.\" entries marked with X<> in POD.  Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.\"
.\" Avoid warning from groff about undefined register 'F'.
.de IX
..
.nr rF 0
.if \n(.g .if rF .nr rF 1
.if (\n(rF:(\n(.g==0)) \{\
.    if \nF \{\
.        de IX
.        tm Index:\\$1\t\\n%\t"\\$2"
..
.        if !\nF==2 \{\
.            nr % 0
.            nr F 2
.        \}
.    \}
.\}
.rr rF
.\" ========================================================================
.\"
.IX Title "CGI::Test 3pm"
.TH CGI::Test 3pm "2021-01-08" "perl v5.32.0" "User Contributed Perl Documentation"
.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH "NAME"
CGI::Test \- CGI regression test framework
.SH "SYNOPSIS"
.IX Header "SYNOPSIS"
.Vb 3
\& # In some t/script.t regression test, for instance
\& use CGI::Test;
\& use Test::More tests => 7;
\&
\& my $ct = CGI::Test\->new(
\&    \-base_url   => "http://some.server:1234/cgi\-bin",
\&    \-cgi_dir    => "/path/to/cgi\-bin",
\& );
\&
\& my $page = $ct\->GET("http://some.server:1234/cgi\-bin/script?arg=1");
\& like $page\->content_type, qr|text/html\eb|, "Content type";
\&
\& my $form = $page\->forms\->[0];
\& is $form\->action, "/cgi\-bin/some_target", "Form action URI";
\&
\& my $menu = $form\->menu_by_name("months");
\& ok $menu\->is_selected("January"), "January selected";
\& ok !$menu\->is_selected("March"),  "March not selected";
\& ok $menu\->multiple,               "Menu is multi\-choice";
\&
\& my $send = $form\->submit_by_name("send_form");
\& ok defined $send, "Send form defined";
\&
\& #
\& # Now interact with the CGI
\& #
\&
\& $menu\->select("March");        # "click" on the March label
\& my $answer = $send\->press;     # "click" on the send button
\& 
\& # and make sure we don\*(Aqt get an HTTP error
\& ok $answer\->is_ok, "Answer response";
.Ve
.SH "DESCRIPTION"
.IX Header "DESCRIPTION"
The \f(CW\*(C`CGI::Test\*(C'\fR module provides a \s-1CGI\s0 regression test framework which
allows you to run your \s-1CGI\s0 programs offline, i.e. outside a web server,
and interact with them programmatically, without the need to type data
and click from a web browser.
.PP
If you're using the \f(CW\*(C`CGI\*(C'\fR module, you may be familiar with its offline
testing mode.  However, this mode is appropriate for simple things, and
there is no support for conducting a full session with a stateful script.
\&\f(CW\*(C`CGI::Test\*(C'\fR fills this gap by providing the necessary infrastructure to
run \s-1CGI\s0 scripts, then parse the output to construct objects that can be
queried, and on which you can interact to \*(L"play\*(R" with the script's control
widgets, finally submitting data back.  And so on...
.PP
Note that the \s-1CGI\s0 scripts you can test with \f(CW\*(C`CGI::Test\*(C'\fR need not be
implemented in Perl at all.  As far as this framework is concerned, \s-1CGI\s0
scripts are executables that are run on a CGI-like environment and which
produce an output.
.PP
To use the \f(CW\*(C`CGI::Test\*(C'\fR framework, you need to configure a \f(CW\*(C`CGI::Test\*(C'\fR
object to act like a web server, by providing the \s-1URL\s0 base where
\&\s-1CGI\s0 scripts lie on this pseudo-server, and which physical directory
corresponds to that \s-1URL\s0 base.
.PP
From then on, you may issue \s-1GET\s0 and \s-1POST\s0 requests giving an \s-1URL,\s0 and
the pseudo-server returns a \f(CW\*(C`CGI::Test::Page\*(C'\fR object representing the
outcome of the request.  This page may be an error, plain text, some
binary data, or an \s-1HTML\s0 page (see CGI::Test::Page for details).
.PP
The latter (an \s-1HTML\s0 page) can contain one or more \s-1CGI\s0 forms (identified
by \f(CW\*(C`<FORM>\*(C'\fR tags), which are described by instances of
\&\f(CW\*(C`CGI::Test::Form\*(C'\fR objects (see CGI::Test::Form for details).
.PP
Forms can be queried to see whether they contain a particular type
of widget (menu, text area, button, etc...), of a particular name
(that's the \s-1CGI\s0 parameter name).  Once found, one may interact with
a widget as the user would from a browser.  Widgets are described by
polymorphic objects which conform to the \f(CW\*(C`CGI::Test::Form::Widget\*(C'\fR type.
The specific interaction that is offered depends on the dynamic type of
the object (see CGI::Test::Form::Widget for details).
.PP
An interaction with a form ends by a submission of the form data to the
server, and getting a reply back.  This is done by pressing a submit button,
and the \fBpress()\fR routine returns a new page.  Naturally, no server is
contacted at all within the \f(CW\*(C`CGI::Test\*(C'\fR framework, and the \s-1CGI\s0 script is
ran through a proper call to one of the \s-1GET/POST\s0 method on the
\&\f(CW\*(C`CGI::Test\*(C'\fR object.
.SH "INTERFACE"
.IX Header "INTERFACE"
.SS "Creation Interface"
.IX Subsection "Creation Interface"
The creation routine \f(CW\*(C`new()\*(C'\fR takes the following mandatory parameters:
.ie n .IP """\-base_url"" => \fI\s-1URL\s0 of the cgi-bin directory\fR" 4
.el .IP "\f(CW\-base_url\fR => \fI\s-1URL\s0 of the cgi-bin directory\fR" 4
.IX Item "-base_url => URL of the cgi-bin directory"
Defines the \s-1URL\s0 domain which is handled by \f(CW\*(C`CGI::Test\*(C'\fR.
This is the \s-1URL\s0 of the \f(CW\*(C`cgi\-bin\*(C'\fR directory.
.Sp
Note that there is no need to have something actually running on the
specified host or port, and the server name can be any host name,
whether it exists or not.  For instance, if you say:
.Sp
.Vb 1
\&    \-base_url => "http://foo.example.com:70/cgi\-bin"
.Ve
.Sp
you simply declare that the \f(CW\*(C`CGI::Test\*(C'\fR object will know how to handle
a \s-1GET\s0 request for, say:
.Sp
.Vb 1
\&    http://foo.example.com:70/cgi\-bin/script
.Ve
.Sp
and it will do so \fIinternally\fR, without contacting \f(CW\*(C`foo.example.com\*(C'\fR
on port 70...
.ie n .IP """\-cgi_dir"" => \fIpath to the cgi-bin directory\fR" 4
.el .IP "\f(CW\-cgi_dir\fR => \fIpath to the cgi-bin directory\fR" 4
.IX Item "-cgi_dir => path to the cgi-bin directory"
Defines the physical path corresponding to the \f(CW\*(C`cgi\-bin\*(C'\fR directory defined
by the \f(CW\*(C`\-base_url\*(C'\fR parameter.
.Sp
For instance, given the settings:
.Sp
.Vb 2
\&    \-base_url => "http://foo.example.com:70/cgi\-bin",
\&    \-cgi_dir  => "/home/ram/cgi/test"
.Ve
.Sp
then requesting
.Sp
.Vb 1
\&    http://foo.example.com:70/cgi\-bin/script
.Ve
.Sp
will actually run
.Sp
.Vb 1
\&    /home/ram/cgi/test/script
.Ve
.Sp
Those things are really easier to understand via examples than via
formal descriptions, aren't they?
.PP
The following optional arguments may also be provided:
.ie n .IP """\-cgi_env"" => \fI\s-1HASH\s0 ref\fR" 4
.el .IP "\f(CW\-cgi_env\fR => \fI\s-1HASH\s0 ref\fR" 4
.IX Item "-cgi_env => HASH ref"
Defines additional environment variables that must be set, or changes
hardwirted defaults.  Some variables like \f(CW\*(C`CONTENT_TYPE\*(C'\fR really depend
on the request and will be dynamically computed by \f(CW\*(C`CGI::Test\*(C'\fR.
.Sp
For instance:
.Sp
.Vb 4
\&    \-cgi_env => {
\&        HTTP_USER_AGENT     => "Mozilla/4.76",
\&        AUTH_TYPE           => "Digest",
\&    }
.Ve
.Sp
See \*(L"\s-1CGI ENVIRONMENT VARIABLES\*(R"\s0 for more details on which environment
variables are defined, and which may be superseded.
.ie n .IP """\-doc_dir"" => \fIpath to document tree\fR" 4
.el .IP "\f(CW\-doc_dir\fR => \fIpath to document tree\fR" 4
.IX Item "-doc_dir => path to document tree"
This defines the root directory of the \s-1HTTP\s0 server, for path translation.
It defaults to \f(CW\*(C`/var/www\*(C'\fR.
.Sp
\&\fB\s-1NOTE\s0\fR: \f(CW\*(C`CGI::Test\*(C'\fR only serves \s-1CGI\s0 scripts for now, so this setting
is not terribly useful, unless you care about \f(CW\*(C`PATH_TRANSLATED\*(C'\fR.
.ie n .IP """\-tmp_dir"" => \fIpath to temporary directory\fR" 4
.el .IP "\f(CW\-tmp_dir\fR => \fIpath to temporary directory\fR" 4
.IX Item "-tmp_dir => path to temporary directory"
The temporary directory to use for internal files created while processing
requests.  Defaults to the value of the environment variable \f(CW\*(C`TMPDIR\*(C'\fR,
or \f(CW\*(C`/tmp\*(C'\fR if it is not set.
.SS "Object Interface"
.IX Subsection "Object Interface"
The following methods, listed in alphabetical order, are available:
.ie n .IP """GET"" \fIurl_string\fR [, \fIauth_user\fR]" 4
.el .IP "\f(CWGET\fR \fIurl_string\fR [, \fIauth_user\fR]" 4
.IX Item "GET url_string [, auth_user]"
Issues an \s-1HTTP GET\s0 request of the specified \s-1URL,\s0 given as the string
\&\fIurl_string\fR.  It must be in the http scheme, and must lie within the
configured \s-1CGI\s0 space (i.e. under the base \s-1URL\s0 given at creation time
via \f(CW\*(C`\-base_url\*(C'\fR).
.Sp
Optionally, you may specify the name of an authenticated user as the
\&\fIauth_user\fR string. \f(CW\*(C`CGI::Test\*(C'\fR will simply setup the \s-1CGI\s0 environment
variable \f(CW\*(C`REMOTE_USER\*(C'\fR accordingly.  Since we're in a testing framework,
you can pretend to be anyone you like.  See \*(L"\s-1CGI ENVIRONMENT VARIABLES\*(R"\s0
for more information on environment variables, and in particular
\&\f(CW\*(C`AUTH_TYPE\*(C'\fR.
.Sp
\&\f(CW\*(C`GET\*(C'\fR returns a \f(CW\*(C`CGI::Test::Page\*(C'\fR polymorphic object, i.e. an object whose
dynamic type is an heir of \f(CW\*(C`CGI::Test::Page\*(C'\fR.  See CGI::Test::Page for
more information on this class hierarchy.
.ie n .IP """POST"" \fIurl_string\fR, \fIinput_data\fR [, \fIauth_user\fR]" 4
.el .IP "\f(CWPOST\fR \fIurl_string\fR, \fIinput_data\fR [, \fIauth_user\fR]" 4
.IX Item "POST url_string, input_data [, auth_user]"
Issues an \s-1HTTP POST\s0 request of the specified \s-1URL.\s0  See \f(CW\*(C`GET\*(C'\fR above for
a discussion on \fIurl_string\fR and \fIauth_user\fR, which applies to \f(CW\*(C`POST\*(C'\fR
as well.
.Sp
The \fIinput_data\fR parameter must be a \f(CW\*(C`CGI::Test::Input\*(C'\fR object.
It specifies the \s-1CGI\s0 parameters to be sent to the script.  Users normally
don't issue \s-1POST\s0 requests manually: they are the result of submits on
forms, which are obtained via an initial \s-1GET.\s0  Nonetheless, you can
create your own input easily and issue a \*(L"faked\*(R" \s-1POST\s0 request, to see
how your script might react to inconsistent (and probably malicious)
input for instance.  See CGI::Test::Input to learn how to construct
suitable input.
.Sp
\&\f(CW\*(C`POST\*(C'\fR returns a \f(CW\*(C`CGI::Test::Page\*(C'\fR polymorphic object, like \f(CW\*(C`GET\*(C'\fR does.
.ie n .IP """base_path""" 4
.el .IP "\f(CWbase_path\fR" 4
.IX Item "base_path"
The base path in the \s-1URL\s0 space of the base \s-1URL\s0 configured at creation time.
It's the \s-1URL\s0 with the scheme, host and port information removed.
.ie n .IP """cgi_dir""" 4
.el .IP "\f(CWcgi_dir\fR" 4
.IX Item "cgi_dir"
The configured \s-1CGI\s0 root directory where scripts to be run are held.
.ie n .IP """doc_dir""" 4
.el .IP "\f(CWdoc_dir\fR" 4
.IX Item "doc_dir"
The configured document root directory.
.ie n .IP """host_port""" 4
.el .IP "\f(CWhost_port\fR" 4
.IX Item "host_port"
The host and port of the base \s-1URL\s0 you configured at creation time.
.ie n .IP """split_uri"" \fI\s-1URI\s0\fR" 4
.el .IP "\f(CWsplit_uri\fR \fI\s-1URI\s0\fR" 4
.IX Item "split_uri URI"
Splits an \s-1URI\s0 object into server (host and port), path and query components.
The path is simplified using \s-1UNIX\s0 semantics, i.e. \f(CW\*(C`/./\*(C'\fR is ignored and
stripped, and \f(CW\*(C`/../\*(C'\fR is resolved by forgetting the path component that
immediately precedes it (no attempt is made to make sure the translated path
was indeed pointing to an existing directory: simplification happens in the
path space).
.Sp
Returns the list (host, path, query).
.ie n .IP """tmp_dir""" 4
.el .IP "\f(CWtmp_dir\fR" 4
.IX Item "tmp_dir"
The temporary directory that is being used.
.ie n .IP """http_headers""" 4
.el .IP "\f(CWhttp_headers\fR" 4
.IX Item "http_headers"
Returns hashref with parsed \s-1HTTP\s0 headers received from \s-1CGI\s0 script.
.SH "CGI ENVIRONMENT VARIABLES"
.IX Header "CGI ENVIRONMENT VARIABLES"
The \s-1CGI\s0 protocol defines a set of environment variables which are to be set
by the web server before invoking the script.  The environment created by
\&\f(CW\*(C`CGI::Test\*(C'\fR conforms to the \s-1CGI/1.1\s0 specifications.
.PP
Here is a list of all the known variables.  Some of those are marked
\&\fIread-only\fR.  It means you may choose to set them via the \f(CW\*(C`\-cgi_env\*(C'\fR
switch of the \f(CW\*(C`new()\*(C'\fR routine, but your settings will have no effect and
\&\f(CW\*(C`CGI::Test\*(C'\fR will always compute a suitable value.
.PP
Variables are listed in alphabetical order:
.ie n .IP """AUTH_TYPE""" 4
.el .IP "\f(CWAUTH_TYPE\fR" 4
.IX Item "AUTH_TYPE"
The authentication scheme used to authenticate the user given by \f(CW\*(C`REMOTE_USER\*(C'\fR.
This variable is not present in the environment if there was no user specified
in the \s-1GET/POST\s0 requests.
.Sp
By default, it is set to \*(L"Basic\*(R" when present.
.ie n .IP """CONTENT_LENGTH""" 4
.el .IP "\f(CWCONTENT_LENGTH\fR" 4
.IX Item "CONTENT_LENGTH"
Read-only variable, giving the length of data to be read on \s-1STDIN\s0 by \s-1POST\s0
requests (as told by \f(CW\*(C`REQUEST_METHOD\*(C'\fR).  If is not present for \s-1GET\s0 requests.
.ie n .IP """CONTENT_TYPE""" 4
.el .IP "\f(CWCONTENT_TYPE\fR" 4
.IX Item "CONTENT_TYPE"
Read-only variable, giving the \s-1MIME\s0 type of data to be read on \s-1STDIN\s0 by \s-1POST\s0
requests (as told by \f(CW\*(C`REQUEST_METHOD\*(C'\fR).  If is not present for \s-1GET\s0 requests.
.ie n .IP """GATEWAY_INTERFACE""" 4
.el .IP "\f(CWGATEWAY_INTERFACE\fR" 4
.IX Item "GATEWAY_INTERFACE"
The Common Gateway Interface (\s-1CGI\s0) version specification.
Defaults to \*(L"\s-1CGI/1.1\*(R".\s0
.ie n .IP """HTTP_ACCEPT""" 4
.el .IP "\f(CWHTTP_ACCEPT\fR" 4
.IX Item "HTTP_ACCEPT"
The set of Content-Type that are said to be accepted by the client issuing
the \s-1HTTP\s0 request.  Since there is no browser making any request here, the
default is set to \*(L"*/*\*(R".
.Sp
It is up to your script to honour the value of this variable if it wishes to
be nice with the client.
.ie n .IP """HTTP_ACCEPT_CHARSET""" 4
.el .IP "\f(CWHTTP_ACCEPT_CHARSET\fR" 4
.IX Item "HTTP_ACCEPT_CHARSET"
The charset that is said to be accepted by the client issuing the \s-1HTTP\s0
request.  Since there is no browser making any request here, the
default is set to \*(L"iso\-8859\-1\*(R".
.ie n .IP """HTTP_CONNECTION""" 4
.el .IP "\f(CWHTTP_CONNECTION\fR" 4
.IX Item "HTTP_CONNECTION"
Whether the connection should be kept alive by the server or closed after
this request.  Defaults to \*(L"Close\*(R", but since there's no connection and
no real client...
.ie n .IP """HTTP_HOST""" 4
.el .IP "\f(CWHTTP_HOST\fR" 4
.IX Item "HTTP_HOST"
This is the host processing the \s-1HTTP\s0 request.
It is a read-only variable, set to the hostname and port parts of the
requested \s-1URL.\s0
.ie n .IP """HTTP_USER_AGENT""" 4
.el .IP "\f(CWHTTP_USER_AGENT\fR" 4
.IX Item "HTTP_USER_AGENT"
The user agent tag string.  This can be used by scripts to emit code that
can be understood by the client, and is also further abused to derive the
\&\s-1OS\s0 type where the user agent runs.
.Sp
In order to be as neutral as possible, it is set to \*(L"CGI::Test\*(R" by default.
.ie n .IP """PATH_INFO""" 4
.el .IP "\f(CWPATH_INFO\fR" 4
.IX Item "PATH_INFO"
Read-only variable set to the extra path information part of the requested \s-1URL.\s0
Always present, even if empty.
.ie n .IP """PATH_TRANSLATED""" 4
.el .IP "\f(CWPATH_TRANSLATED\fR" 4
.IX Item "PATH_TRANSLATED"
This read-only variable is only present when there is a non-empty \f(CW\*(C`PATH_INFO\*(C'\fR
variable.  It is simply set to the value of \f(CW\*(C`PATH_INFO\*(C'\fR with the document
rootdir path prepended to it (the value of the \f(CW\*(C`\-doc_dir\*(C'\fR creation argument).
.ie n .IP """QUERY_STRING""" 4
.el .IP "\f(CWQUERY_STRING\fR" 4
.IX Item "QUERY_STRING"
This very important read-only variable is the query string present in the
requested \s-1URL.\s0  Note that it may very well be set even for a \s-1POST\s0 request.
.ie n .IP """REMOTE_ADDR""" 4
.el .IP "\f(CWREMOTE_ADDR\fR" 4
.IX Item "REMOTE_ADDR"
The \s-1IP\s0 address of the client making the requst.  Can be used to implement
an access policy from within the script.  Here, given that there's no real
client, the default is set to \*(L"127.0.0.1\*(R", which is the \s-1IP\s0 of the local
loopback interface.
.ie n .IP """REMOTE_HOST""" 4
.el .IP "\f(CWREMOTE_HOST\fR" 4
.IX Item "REMOTE_HOST"
The DNS-translated hostname of the \s-1IP\s0 address held in \f(CW\*(C`REMOTE_ADDR\*(C'\fR.
Here, for testing purposes, it is not computed after \f(CW\*(C`REMOTE_ADDR\*(C'\fR but can
be freely set.  Defaults to \*(L"localhost\*(R".
.ie n .IP """REMOTE_USER""" 4
.el .IP "\f(CWREMOTE_USER\fR" 4
.IX Item "REMOTE_USER"
This read-only variable is only present when making an authenticated \s-1GET\s0 or
\&\s-1POST\s0 request.  Its value is the name of the user we are supposed to have
successfully authenticated, using the scheme held in \f(CW\*(C`AUTH_TYPE\*(C'\fR.
.ie n .IP """REQUEST_METHOD""" 4
.el .IP "\f(CWREQUEST_METHOD\fR" 4
.IX Item "REQUEST_METHOD"
Read-only variable, whose value is either \f(CW\*(C`GET\*(C'\fR or \f(CW\*(C`POST\*(C'\fR.
.ie n .IP """SCRIPT_FILENAME""" 4
.el .IP "\f(CWSCRIPT_FILENAME\fR" 4
.IX Item "SCRIPT_FILENAME"
Read-only variable set to the filesystem path of the \s-1CGI\s0 script being run.
.ie n .IP """SCRIPT_NAME""" 4
.el .IP "\f(CWSCRIPT_NAME\fR" 4
.IX Item "SCRIPT_NAME"
Read-only variable set to the virtual  path of the \s-1CGI\s0 script being run,
i.e. the path given in the requested \s-1URL.\s0
.ie n .IP """SERVER_NAME""" 4
.el .IP "\f(CWSERVER_NAME\fR" 4
.IX Item "SERVER_NAME"
The host name running the server, which defaults to the host name present
in the base \s-1URL,\s0 provided at creation time as the \f(CW\*(C`\-base_url\*(C'\fR argument.
.ie n .IP """SERVER_PORT""" 4
.el .IP "\f(CWSERVER_PORT\fR" 4
.IX Item "SERVER_PORT"
The port where the server listens, which defaults to the port present
in the base \s-1URL,\s0 provided at creation time as the \f(CW\*(C`\-base_url\*(C'\fR argument.
If no port was explicitely given, 80 is assumed.
.ie n .IP """SERVER_PROTOCOL""" 4
.el .IP "\f(CWSERVER_PROTOCOL\fR" 4
.IX Item "SERVER_PROTOCOL"
The protocol which must be followed when replying to the client request.
Set to \*(L"\s-1HTTP/1.1\*(R"\s0 by default.
.ie n .IP """SERVER_SOFTWARE""" 4
.el .IP "\f(CWSERVER_SOFTWARE\fR" 4
.IX Item "SERVER_SOFTWARE"
The name of the server software.  Defaults to \*(L"CGI::Test\*(R".
.SH "BUGS"
.IX Header "BUGS"
There are some, most probably.  Please notify me about them.
.PP
The following limitations (in decreasing amount of importance)
are known and may be lifted one day \*(-- patches welcome:
.IP "\(bu" 4
There is no support for cookies.  A \s-1CGI\s0 installing cookies and expecting
them to be resent on further invocations to friendly scripts is bound
to disappointment.
.IP "\(bu" 4
There is no support for plain document retrieval: only \s-1CGI\s0 scripts can
be fetched by an \s-1HTTP\s0 request for now.
.SH "PUBLIC REPOSITORY"
.IX Header "PUBLIC REPOSITORY"
CGI::Test now has a publicly accessible Git server provided by Github.com:
<http://github.com/nohuhu/CGI\-Test>
.SH "REPORTING BUGS"
.IX Header "REPORTING BUGS"
Please use Github issue tracker to open bug reports and maintenance
requests.
.SH "AUTHORS"
.IX Header "AUTHORS"
The original author is Raphael Manfredi.
.PP
Steven Hilton was long time maintainer of this module.
.PP
Current maintainer is Alex Tokarev \fI<tokarev@cpan.org>\fR.
.SH "LICENSE"
.IX Header "LICENSE"
This program is free software; you can redistribute it and/or modify
it under the terms of the Artistic License, a copy of which can be
found with Perl 5.6.0.
.PP
This program is distributed in the hope that it will be useful,
but \s-1WITHOUT ANY WARRANTY\s0; without even the implied warranty of
\&\s-1MERCHANTABILITY\s0 or \s-1FITNESS FOR A PARTICULAR PURPOSE.\s0  See the
Artistic License for more details.
.SH "SEE ALSO"
.IX Header "SEE ALSO"
\&\s-1\fBCGI\s0\fR\|(3), \fBCGI::Test::Page\fR\|(3), \fBCGI::Test::Form\fR\|(3), \fBCGI::Test::Input\fR\|(3),
\&\fBCGI::Test::Form::Widget\fR\|(3), \fBHTTP::Status\fR\|(3), \s-1\fBURI\s0\fR\|(3).