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 / 䆊䌷䈹䈙䏵-䞅䞆䞀㡆䞃䄦䠥 / _57af610ce8e5783489dd5bf6864e2ee7 < prev next >

Wrap

Text File | 2000-03-23 | 11.6 KB | 282 lines

<HTML> <HEAD> <TITLE>HTTP::Headers - Class encapsulating HTTP Message headers</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::Headers - Class encapsulating HTTP Message headers </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="#convenience methods">CONVENIENCE METHODS</A></LI> <LI><A HREF="#copyright">COPYRIGHT</A></LI> </UL>  <HR> <H1><A NAME="name">NAME</A></H1> HTTP::Headers - Class encapsulating HTTP Message headers <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::Headers; $h = new HTTP::Headers;</PRE> <HR> <H1><A NAME="description">DESCRIPTION</A></H1> The <CODE>HTTP::Headers</CODE> class encapsulates HTTP-style message headers. The headers consist of attribute-value pairs, which may be repeated, and which are printed in a particular order. Instances of this class are usually created as member variables of the <CODE>HTTP::Request</CODE> and <CODE>HTTP::Response</CODE> classes, internal to the library. The following methods are available: <DL> <DT><A NAME="item_%24h_%3D_new_HTTP%3A%3AHeaders">$h = new HTTP::Headers</A> <DD> Constructs a new <CODE>HTTP::Headers</CODE> object. You might pass some initial attribute-value pairs as parameters to the constructor. E.g.: <PRE> $h = new HTTP::Headers Date => 'Thu, 03 Feb 1994 00:00:00 GMT', Content_Type => 'text/html; version=3.2', Content_Base => '<A HREF="http://www.sn.no/">http://www.sn.no/</A>';</PRE> <DT><A NAME="item_header">$h->header($field [=> $value],...)</A> <DD> Get or set the value of a header. The header field name is not case sensitive. To make the life easier for perl users who wants to avoid quoting before the => operator, you can use '_' as a synonym for '-' in header names (this behaviour can be suppressed by setting $HTTP::Headers::TRANSLATE_UNDERSCORE to a FALSE value). The <A HREF="#item_header"><CODE>header()</CODE></A> method accepts multiple ($field => $value) pairs, so you can update several fields with a single invocation. The optional $value argument may be a scalar or a reference to a list of scalars. If the $value argument is undefined or not given, then the header is not modified. The old value of the last of the $field values is returned. Multi-valued fields will be concatenated with ``,'' as separator in scalar context. <PRE> $header->header(MIME_Version => '1.0', User_Agent => 'My-Web-Client/0.01'); $header->header(Accept => "text/html, text/plain, image/*"); $header->header(Accept => [qw(text/html text/plain image/*)]); @accepts = $header->header('Accept');</PRE> <DT><A NAME="item_scan">$h-><CODE>scan(\&doit)</CODE></A> <DD> Apply a subroutine to each header in turn. The callback routine is called with two parameters; the name of the field and a single value. If the header has more than one value, then the routine is called once for each value. The field name passed to the callback routine has case as suggested by HTTP Spec, and the headers will be visited in the recommended ``Good Practice'' order. <DT><A NAME="item_as_string">$h-><CODE>as_string([$endl])</CODE></A> <DD> Return the header fields as a formatted MIME header. Since it internally uses the <A HREF="#item_scan"><CODE>scan()</CODE></A> method to build the string, the result will use case as suggested by HTTP Spec, and it will follow recommended ``Good Practice'' of ordering the header fieds. Long header values are not folded. The optional parameter specifies the line ending sequence to use. The default is <CODE>"\n"</CODE>. Embedded ``\n'' characters in the header will be substitued with this line ending sequence. <DT><A NAME="item_push_header">$h->push_header($field, $val)</A> <DD> Add a new field value of the specified header. The header field name is not case sensitive. The field need not already have a value. Previous values for the same field are retained. The argument may be a scalar or a reference to a list of scalars. <PRE> $header->push_header(Accept => 'image/jpeg');</PRE> <DT><A NAME="item_remove_header">$h-><CODE>remove_header($field,...)</CODE></A> <DD> This function removes the headers with the specified names. <DT><A NAME="item_clone">$h->clone</A> <DD> Returns a copy of this HTTP::Headers object. </DL> <HR> <H1><A NAME="convenience methods">CONVENIENCE METHODS</A></H1> The most frequently used headers can also be accessed through the following convenience methods. These methods can both be used to read and to set the value of a header. The header value is set if you pass an argument to the method. The old header value is always returned. Methods that deal with dates/times always convert their value to system time (seconds since Jan 1, 1970) and they also expect this kind of value when the header value is set. <DL> <DT><A NAME="item_date">$h->date</A> <DD> This header represents the date and time at which the message was originated. E.g.: <PRE> $h->date(time); # set current date</PRE> <DT><A NAME="item_expires">$h->expires</A> <DD> This header gives the date and time after which the entity should be considered stale. <DT><A NAME="item_if_modified_since">$h->if_modified_since</A> <DD> <DT><A NAME="item_if_unmodified_since">$h->if_unmodified_since</A> <DD> This header is used to make a request conditional. If the requested resource has (not) been modified since the time specified in this field, then the server will return a <CODE>"304 Not Modified"</CODE> response instead of the document itself. <DT><A NAME="item_last_modified">$h->last_modified</A> <DD> This header indicates the date and time at which the resource was last modified. E.g.: <PRE> # check if document is more than 1 hour old if ($h->last_modified < time - 60*60) { ... }</PRE> <DT><A NAME="item_content_type">$h->content_type</A> <DD> The Content-Type header field indicates the media type of the message content. E.g.: <PRE> $h->content_type('text/html');</PRE> The value returned will be converted to lower case, and potential parameters will be chopped off and returned as a separate value if in an array context. This makes it safe to do the following: <PRE> if ($h->content_type eq 'text/html') { # we enter this place even if the real header value happens to # be 'TEXT/HTML; version=3.0' ... }</PRE> <DT><A NAME="item_content_encoding">$h->content_encoding</A> <DD> The Content-Encoding header field is used as a modifier to the media type. When present, its value indicates what additional encoding mechanism has been applied to the resource. <DT><A NAME="item_content_length">$h->content_length</A> <DD> A decimal number indicating the size in bytes of the message content. <DT><A NAME="item_content_language">$h->content_language</A> <DD> The natural <CODE>language(s)</CODE> of the intended audience for the message content. The value is one or more language tags as defined by RFC 1766. Eg. ``no'' for Norwegian and ``en-US'' for US-English. <DT><A NAME="item_title">$h->title</A> <DD> The title of the document. In libwww-perl this header will be initialized automatically from the <TITLE>...</TITLE> element of HTML documents. This header is no longer part of the HTTP standard. <DT><A NAME="item_user_agent">$h->user_agent</A> <DD> This header field is used in request messages and contains information about the user agent originating the request. E.g.: <PRE> $h->user_agent('Mozilla/1.2');</PRE> <DT><A NAME="item_server">$h->server</A> <DD> The server header field contains information about the software being used by the originating server program handling the request. <DT><A NAME="item_from">$h->from</A> <DD> This header should contain an Internet e-mail address for the human user who controls the requesting user agent. The address should be machine-usable, as defined by RFC822. E.g.: <PRE> $h->from('Gisle Aas <aas@sn.no>');</PRE> <DT><A NAME="item_referer">$h->referer</A> <DD> Used to specify the address (URI) of the document from which the requested resouce address was obtained. <DT><A NAME="item_www_authenticate">$h->www_authenticate</A> <DD> This header must be included as part of a ``401 Unauthorized'' response. The field value consist of a challenge that indicates the authentication scheme and parameters applicable to the requested URI. <DT><A NAME="item_proxy_authenticate">$h->proxy_authenticate</A> <DD> This header must be included in a ``407 Proxy Authentication Required'' response. <DT><A NAME="item_authorization">$h->authorization</A> <DD> <DT><A NAME="item_proxy_authorization">$h->proxy_authorization</A> <DD> A user agent that wishes to authenticate itself with a server or a proxy, may do so by including these headers. <DT><A NAME="item_authorization_basic">$h->authorization_basic</A> <DD> This method is used to get or set an authorization header that use the ``Basic Authentication Scheme''. In array context it will return two values; the user name and the password. In scalar context it will return ``uname:password'' as a single string value. When used to set the header value, it expects two arguments. E.g.: <PRE> $h->authorization_basic($uname, $password);</PRE> The method will croak if the $uname contains a colon ':'. <DT><A NAME="item_proxy_authorization_basic">$h->proxy_authorization_basic</A> <DD> Same as <A HREF="#item_authorization_basic"><CODE>authorization_basic()</CODE></A> but will set the ``Proxy-Authorization'' header instead. </DL> <HR> <H1><A NAME="copyright">COPYRIGHT</A></H1> Copyright 1995-1998 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::Headers - Class encapsulating HTTP Message headers </TD></TR> </TABLE> </BODY> </HTML>