Chip 2000 May

home *** CD-ROM | disk | FTP | other *** search

/ Chip 2000 May / Chip_2000-05_cd1.bin / zkuste / Perl / ActivePerl-5.6.0.613.msi / 䆊䌷䈹䈙䏵-䞅䞆䞀㡆䞃䄦䠥 / _daa6079b63a23f82396c6639e9080228 < prev next >

Wrap

Text File | 2000-03-23 | 7.7 KB | 193 lines

<HTML> <HEAD> <TITLE>HTTP::Response - Class encapsulating HTTP Responses</TITLE> <LINK REL="stylesheet" HREF="../../../Active.css" TYPE="text/css"> <LINK REV="made" HREF="mailto:"> </HEAD> <BODY> <TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0 WIDTH=100%> <TR><TD CLASS=block VALIGN=MIDDLE WIDTH=100% BGCOLOR="#cccccc"> HTTP::Response - Class encapsulating HTTP Responses </TD></TR> </TABLE> <A NAME="__index__"></A>  <UL> <LI><A HREF="#name">NAME</A></LI><LI><A HREF="#supportedplatforms">SUPPORTED PLATFORMS</A></LI> <LI><A HREF="#synopsis">SYNOPSIS</A></LI> <LI><A HREF="#description">DESCRIPTION</A></LI> <LI><A HREF="#copyright">COPYRIGHT</A></LI> </UL>  <HR> <H1><A NAME="name">NAME</A></H1> HTTP::Response - Class encapsulating HTTP Responses <HR> <H1><A NAME="supportedplatforms">SUPPORTED PLATFORMS</A></H1> <UL> <LI>Linux</LI> <LI>Solaris</LI> <LI>Windows</LI> </UL> <HR> <H1><A NAME="synopsis">SYNOPSIS</A></H1> <PRE> require HTTP::Response;</PRE> <HR> <H1><A NAME="description">DESCRIPTION</A></H1> The <CODE>HTTP::Response</CODE> class encapsulates HTTP style responses. A response consists of a response line, some headers, and (potentially empty) content. Note that the LWP library also uses HTTP style responses for non-HTTP protocol schemes. Instances of this class are usually created and returned by the <A HREF="#item_request"><CODE>request()</CODE></A> method of an <CODE>LWP::UserAgent</CODE> object: <PRE> #... $response = $ua->request($request) if ($response->is_success) { print $response->content; } else { print $response->error_as_HTML; }</PRE> <CODE>HTTP::Response</CODE> is a subclass of <CODE>HTTP::Message</CODE> and therefore inherits its methods. The inherited methods most often used are header(), push_header(), remove_header(), headers_as_string(), and content(). The header convenience methods are also available. See <A HREF="../../../site/lib/HTTP/Message.html">the HTTP::Message manpage</A> for details. The following additional methods are available: <DL> <DT><A NAME="item_new">$r = HTTP::Response->new($rc, [$msg, [$header, [$content]]])</A> <DD> Constructs a new <CODE>HTTP::Response</CODE> object describing a response with response code <CODE>$rc</CODE> and optional message <CODE>$msg</CODE>. The message is a short human readable single line string that explains the response code. <DT><A NAME="item_code">$r-><CODE>code([$code])</CODE></A> <DD> <DT><A NAME="item_message">$r-><CODE>message([$message])</CODE></A> <DD> <DT><A NAME="item_request">$r-><CODE>request([$request])</CODE></A> <DD> <DT><A NAME="item_previous">$r-><CODE>previous([$previousResponse])</CODE></A> <DD> These methods provide public access to the object attributes. The first two contain respectively the response code and the message of the response. The request attribute is a reference the request that caused this response. It does not have to be the same request as passed to the $ua-><A HREF="#item_request"><CODE>request()</CODE></A> method, because there might have been redirects and authorization retries in between. The previous attribute is used to link together chains of responses. You get chains of responses if the first response is redirect or unauthorized. <DT><A NAME="item_status_line">$r->status_line</A> <DD> Returns the string ``<code> <message>''. If the message attribute is not set then the official name of <code> (see <A HREF="../../../site/lib/HTTP/Status.html">the HTTP::Status manpage</A>) is substituted. <DT><A NAME="item_base">$r->base</A> <DD> Returns the base URL for this response. The return value will be a reference to a URI object. The base URL is obtained from one the following sources (in priority order): <OL> <LI> Embedded in the document content, for instance <BASE HREF=``...''> in HTML documents. <LI> A ``Content-Base:'' or a ``Content-Location:'' header in the response. For backwards compatability with older HTTP implementations we will also look for the ``Base:'' header. <LI> The URL used to request this response. This might not be the original URL that was passed to $ua-><A HREF="#item_request"><CODE>request()</CODE></A> method, because we might have received some redirect responses first. </OL> When the LWP protocol modules produce the HTTP::Response object, then any base URL embedded in the document (step 1) will already have initialized the ``Content-Base:'' header. This means that this method only performs the last 2 steps (the content is not always available either). <DT><A NAME="item_as_string">$r->as_string</A> <DD> Returns a textual representation of the response. Mainly useful for debugging purposes. It takes no arguments. <DT><A NAME="item_is_info">$r->is_info</A> <DD> <DT><A NAME="item_is_success">$r->is_success</A> <DD> <DT><A NAME="item_is_redirect">$r->is_redirect</A> <DD> <DT><A NAME="item_is_error">$r->is_error</A> <DD> These methods indicate if the response was informational, sucessful, a redirection, or an error. <DT><A NAME="item_error_as_HTML">$r-><CODE>error_as_HTML()</CODE></A> <DD> Returns a string containing a complete HTML document indicating what error occurred. This method should only be called when $r->is_error is TRUE. <DT><A NAME="item_current_age">$r->current_age</A> <DD> Calculates the ``current age'' of the response as specified by <draft-ietf-http-v11-spec-07> section 13.2.3. The age of a response is the time since it was sent by the origin server. The returned value is a number representing the age in seconds. <DT><A NAME="item_freshness_lifetime">$r->freshness_lifetime</A> <DD> Calculates the ``freshness lifetime'' of the response as specified by <draft-ietf-http-v11-spec-07> section 13.2.4. The ``freshness lifetime'' is the length of time between the generation of a response and its expiration time. The returned value is a number representing the freshness lifetime in seconds. If the response does not contain an ``Expires'' or a ``Cache-Control'' header, then this function will apply some simple heuristic based on 'Last-Modified' to determine a suitable lifetime. <DT><A NAME="item_is_fresh">$r->is_fresh</A> <DD> Returns TRUE if the response is fresh, based on the values of <A HREF="#item_freshness_lifetime"><CODE>freshness_lifetime()</CODE></A> and current_age(). If the response is no longer fresh, then it has to be refetched or revalidated by the origin server. <DT><A NAME="item_fresh_until">$r->fresh_until</A> <DD> Returns the time when this entiy is no longer fresh. </DL> <HR> <H1><A NAME="copyright">COPYRIGHT</A></H1> Copyright 1995-1997 Gisle Aas. This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. <TABLE BORDER=0 CELLPADDING=0 CELLSPACING=0 WIDTH=100%> <TR><TD CLASS=block VALIGN=MIDDLE WIDTH=100% BGCOLOR="#cccccc"> HTTP::Response - Class encapsulating HTTP Responses </TD></TR> </TABLE> </BODY> </HTML>