Lines Matching refs:HTTP
103 # Change this to 1 to suppress redundant HTTP headers
1592 my $protocol = $ENV{SERVER_PROTOCOL} || 'HTTP/1.0';
2995 # and PATH_INFO. Some HTTP servers do sanitise the paths in those
3016 # possibly sanitised by the HTTP server, so in the case of Apache 2:
3180 # cookies are returned exactly as given in the HTTP
3315 # Return the protocol (usually HTTP/1.0)
3319 return $ENV{'SERVER_PROTOCOL'} || 'HTTP/1.0'; # for debugging
3324 # Return the value of an HTTP variable, or
3332 if ( $parameter =~ /^HTTP(?:_|$)/ ) {
3337 return grep { /^HTTP(?:_|$)/ } keys %ENV;
4330 # Process an HTTP request
4338 # Prepare various HTTP responses
4355 HTTP requests and responses. Major features including processing form
4357 and manipulation, and processing and preparing HTTP headers. Some HTML
4387 print $q->header, # create the HTTP header
4404 print header, # create the HTTP header
4500 doesn't recognize. For example, you can produce non-standard HTTP
4508 This will produce the following nonstandard HTTP header:
4510 HTTP/1.0 200 OK
4520 This feature allows you to keep up with the rapidly changing HTTP and
4824 The error messages are formatted as HTTP status codes. You can either
4826 of the HTTP status:
5126 bit checksum of the incoming HTTP headers.
5194 Generally you will produce the HTTP header first, followed by the
5195 document itself. CGI.pm provides functions for generating HTTP
5199 Each of these functions produces a fragment of HTML or HTTP which you
5203 =head2 CREATING A STANDARD HTTP HEADER:
5206 HTTP header. This tells the browser what type of document to expect,
5243 header fields, allowing you to specify any HTTP header you desire.
5328 redirect(). However, most HTTP headers, including those generated by
5336 The B<-status> parameter will set the status of the redirect. HTTP
5380 non-standard HTTP feature which only works with some browsers!>
5393 To create an HTTP-EQUIV type of <meta> tag, use B<-head>, described
5450 And here's how to create an HTTP-EQUIV <meta> tag:
5461 HTTP) header. The block is placed in the header in order to give your
7016 =head1 HTTP COOKIES
7024 them to the browser in the HTTP header. The browser maintains a list
7071 The interface to HTTP cookies is the B<cookie()> method:
7125 The cookie created by cookie() must be incorporated into the HTTP
7180 After writing out the HTTP header, instead of creating a standard
7188 =item 2. Specify the destination for the document in the HTTP header
7673 Called with no arguments returns the list of HTTP environment
7676 like-named HTTP header fields in the request. Called with the name of
7677 an HTTP header field, returns its value. Capitalization and the use
7697 sending the complete HTTP header directly to the browser. This has
7699 of HTTP extensions that are not directly supported by your server,
7896 This error message is actually defined by the HTTP protocol, and is