apache2::request.3

视频监控网络部分的协议ddns,的模块的实现代码,请大家大胆指正.

\&    $req\->param($name)
.Ve
.PP
Get the request parameters (using case-insensitive keys) by
mimicing the \s-1OO\s0 interface of \f(CW\*(C`CGI::param\*(C'\fR.
.PP
.Vb 1
\&    # similar to CGI.pm
\&
\&    my $foo_value   = $req\->param(\*(Aqfoo\*(Aq);
\&    my @foo_values  = $req\->param(\*(Aqfoo\*(Aq);
\&    my @param_names = $req\->param;
\&
\&    # the following differ slightly from CGI.pm
\&
\&    # returns ref to APR::Request::Param::Table object representing
\&    # all (args + body) params
\&    my $table = $req\->param;
\&    @table_keys = keys %$table;
.Ve
.PP
In list context, or when invoked with no arguments as
\&\f(CW\*(C`$req\->param()\*(C'\fR, \f(CW\*(C`param\*(C'\fR induces libapreq2 to read
and parse all remaining data in the request body.
However, \f(CW\*(C`scalar $req\->param("foo")\*(C'\fR is lazy: libapreq2
will only read and parse more data if
.PP
.Vb 2
\&    1) no "foo" param appears in the query string arguments, AND
\&    2) no "foo" param appears in the previously parsed POST data.
.Ve
.PP
In this circumstance libapreq2 will read and parse additional
blocks of the incoming request body until either
.PP
.Vb 2
\&    1) it has found the the "foo" param, or
\&    2) parsing is completed.
.Ve
.PP
Observe that \f(CW\*(C`scalar $req\->param("foo")\*(C'\fR will not raise
an exception if it can locate \*(L"foo\*(R" in the existing body or
args tables, even if the query-string parser or the body parser
has failed.  In all other circumstances \f(CW\*(C`param\*(C'\fR will throw an
Apache2::Request::Error object into $@ should either parser fail.
.PP
.Vb 2
\&    $req\->args_status(1); # set error state for query\-string parser
\&    ok $req\->param_status == 1;
\&
\&    $foo = $req\->param("foo");
\&    ok $foo == 1;
\&    eval { @foo = $req\->param("foo") };
\&    ok $@\->isa("Apache2::Request::Error");
\&    undef $@;
\&    eval { my $not_found = $req\->param("non\-existent\-param") };
\&    ok $@\->isa("Apache2::Request::Error");
\&
\&    $req\->args_status(0); # reset query\-string parser state to "success"
.Ve
.PP
Note: modifications to the \f(CW\*(C`scalar $req\->param()\*(C'\fR table only
affect the returned table object (the underlying C apr_table_t is
\&\fIgenerated\fR from the parse data by \fIapreq_params()\fR).  Modifications
do not affect the actual request data, and will not be seen by other
libapreq2 applications.
.Sh "parms, params"
.IX Subsection "parms, params"
The functionality of these functions is assumed by \f(CW\*(C`param\*(C'\fR,
so they are no longer necessary.  Aliases to \f(CW\*(C`param\*(C'\fR are
provided in this release for backwards compatibility,
however they are deprecated and may be removed from a future
release.
.Sh "body"
.IX Subsection "body"
.Vb 2
\&    $req\->body()
\&    $req\->body($name)
.Ve
.PP
Returns an \fIAPR::Request::Param::Table\fR object containing the \s-1POST\s0 data
parameters of the \fIApache2::Request\fR object.
.PP
.Vb 1
\&    my $body = $req\->body;
.Ve
.PP
An optional name parameter can be passed to return the \s-1POST\s0 data
parameter associated with the given name:
.PP
.Vb 1
\&    my $foo_body = $req\->body("foo");
.Ve
.PP
More generally, \f(CW\*(C`body()\*(C'\fR follows the same pattern as \f(CW\*(C`param()\*(C'\fR
with respect to its return values and argument list.  The main difference
is that modifications to the \f(CW\*(C`scalar $req\->body()\*(C'\fR table affect
the underlying apr_table_t attribute in apreq_request_t, so their impact
will be noticed by all libapreq2 applications during this request.
.Sh "upload"
.IX Subsection "upload"
.Vb 2
\&    $req\->upload()
\&    $req\->upload($name)
.Ve
.PP
Requires \f(CW\*(C`Apache2::Upload\*(C'\fR.  With no arguments, this method
returns an \fIAPR::Request::Param::Table\fR object in scalar context,
or the names of all \fIApache2::Upload\fR objects in list context.
.PP
An optional name parameter can be passed to return the \fIApache2::Upload\fR
object associated with the given name:
.PP
.Vb 1
\&    my $upload = $req\->upload($name);
.Ve
.PP
More generally, \f(CW\*(C`upload()\*(C'\fR follows the same pattern as \f(CW\*(C`param()\*(C'\fR
with respect to its return values and argument list.  The main difference
is that its returned values are Apache2::Upload object refs, not
simple scalars.
.PP
Note: modifications to the \f(CW\*(C`scalar $req\->upload()\*(C'\fR table only
affect the returned table object (the underlying C apr_table_t is
\&\fIgenerated\fR by \fIapreq_uploads()\fR).  They do not affect the actual request
data, and will not be seen by other libapreq2 applications.
.Sh "args_status"
.IX Subsection "args_status"
.Vb 1
\&    $req\->args_status()
.Ve
.PP
Get the \fI\s-1APR\s0\fR status code of the query-string parser.
\&\s-1APR_SUCCESS\s0 on success, error otherwise.
.Sh "body_status"
.IX Subsection "body_status"
.Vb 1
\&    $req\->body_status()
.Ve
.PP
Get the current \fI\s-1APR\s0\fR status code of the parsed \s-1POST\s0 data.
\&\s-1APR_SUCCESS\s0 when parser has completed, \s-1APR_INCOMPLETE\s0 if parser
has more data to parse, \s-1APR_EINIT\s0 if no post data has been parsed,
error otherwise.
.Sh "param_status"
.IX Subsection "param_status"
.Vb 1
\&    $req\->param_status()
.Ve
.PP
In scalar context, this returns \f(CW\*(C`args_status\*(C'\fR if there was
an error during the query-string parse, otherwise this returns
\&\f(CW\*(C`body_status\*(C'\fR, ie
.PP
.Vb 1
\&    $req\->args_status || $req\->body_status
.Ve
.PP
In list context \f(CW\*(C`param_status\*(C'\fR returns the list
\&\f(CW\*(C`(args_status, body_status)\*(C'\fR.
.Sh "parse"
.IX Subsection "parse"
.Vb 1
\&    $req\->parse()
.Ve
.PP
Forces the request to be parsed immediately.  In void context,
this will throw an APR::Request::Error should the either the
query-string or body parser fail. In all other contexts it will
return the two parsers' combined \fI\s-1APR\s0\fR status code
.PP
.Vb 1
\&    $req\->body_status || $req\->args_status
.Ve
.PP
However \f(CW\*(C`parse\*(C'\fR should be avoided in most normal situations.  For example,
in a mod_perl content handler it is more efficient to write
.PP
.Vb 5
\&    sub handler {
\&        my $r = shift;
\&        my $req = Apache2::Request\->new($r);
\&        $r\->discard_request_body;   # efficiently parses the request body
\&        my $parser_status = $req\->body_status;
\&
\&        #...
\&    }
.Ve
.PP
Calling \f(CW\*(C`$r\->discard_request_body\*(C'\fR outside the content handler
is generally a mistake, so use \f(CW\*(C`$req\->parse\*(C'\fR there, but
\&\fBonly as a last resort\fR.  The Apache2::Request \s-1API\s0 is \fBdesigned\fR
around a lazy-parsing scheme, so calling \f(CW\*(C`parse\*(C'\fR should not
affect the behavior of any other methods.
.SH "SUBCLASSING Apache2::Request"
.IX Header "SUBCLASSING Apache2::Request"
If the instances of your subclass are hash references then you can actually
inherit from Apache2::Request as long as the Apache2::Request object is stored in
an attribute called \*(L"r\*(R" or \*(L"_r\*(R". (The Apache2::Request class effectively does the
delegation for you automagically, as long as it knows where to find the
Apache2::Request object to delegate to.)  For example:
.PP
.Vb 7
\&        package MySubClass;
\&        use Apache2::Request;
\&        our @ISA = qw(Apache2::Request);
\&        sub new {
\&                my($class, @args) = @_;
\&                return bless { r => Apache2::Request\->new(@args) }, $class;
\&        }
.Ve
.SH "PORTING from 1.X"
.IX Header "PORTING from 1.X"
This is the complete list of changes to existing methods
from Apache2::Request 1.X.  These issues need to be
addressed when porting 1.X apps to the new 2.X \s-1API\s0.
.IP "\(bu" 4
Apache2::Upload is now a separate module.  Applications
        requiring the upload \s-1API\s0 must \f(CW\*(C`use Apache2::Upload\*(C'\fR in 2.X.
        This is easily addressed by preloading the modules during
        server startup.
.IP "\(bu" 4
You can no longer add (or set or delete) parameters in the
        \f(CW\*(C`scalar $req\->param\*(C'\fR, \f(CW\*(C`scalar $req\->args\*(C'\fR or
        \f(CW\*(C`scalar $req\->body\*(C'\fR tables.  Nor can you add (or set or delete)
        cookies in the \f(CW\*(C`scalar $req\->jar\*(C'\fR table.
.IP "\(bu" 4
\&\f(CW\*(C`instance()\*(C'\fR is now identical to \f(CW\*(C`new()\*(C'\fR, and is now deprecated.  It
        may be removed from a future 2.X release.
.IP "\(bu" 4
\&\f(CW\*(C`param\*(C'\fR includes the functionality of \f(CW\*(C`parms()\*(C'\fR and \f(CW\*(C`params()\*(C'\fR, so
        they are now deprecated and may be removed from a future 2.X release.
.SH "SEE ALSO"
.IX Header "SEE ALSO"
APR::Request::Param, APR::Request::Error, Apache2::Upload,
Apache2::Cookie, \fIAPR::Table\fR\|(3).
.SH "COPYRIGHT"
.IX Header "COPYRIGHT"
.Vb 1
\&  Copyright 2003\-2006  The Apache Software Foundation
\&
\&  Licensed under the Apache License, Version 2.0 (the "License");
\&  you may not use this file except in compliance with the License.
\&  You may obtain a copy of the License at
\&
\&      http://www.apache.org/licenses/LICENSE\-2.0
\&
\&  Unless required by applicable law or agreed to in writing, software
\&  distributed under the License is distributed on an "AS IS" BASIS,
\&  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
\&  See the License for the specific language governing permissions and
\&  limitations under the License.
.Ve