http request
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 3291
HTTP::WebTest 2.04
HTTP::WebTest is a Perl module for testing static and dynamic web content. more>>
HTTP::WebTest is a Perl module for testing static and dynamic web content.
SYNOPSIS
use HTTP::WebTest;
my $webtest = new HTTP::WebTest;
# run test from file
$webtest->run_wtscript(script.wt);
# or (to pass test parameters as method arguments)
$webtest->run_tests($tests);
Introduction
This module runs tests on remote URLs containing Perl/JSP/HTML/JavaScript/etc. and generates a detailed test report. This module can be used "as-is" or its functionality can be extended using plugins. Plugins can define test types and provide additional report capabilities. This module comes with a set of default plugins but can be easily extended with third party plugins.
The wt script is provided for running HTTP::WebTest from the command line.
The test specifications can be read from a parameter file in wtscript format or input as method arguments. The test results can be displayed on the terminal, directed to a file, stored in a scalar variable. The test results can also be emailed. The report can be modified and extended using report plugins.
Each URL/web file is tested by fetching it from the web server using a local instance of an HTTP user agent. The basic test is simply whether or not the fetch was successful. You may also test using literal strings or regular expressions that are either required to exist or forbidden to exist in the fetched page. You may also specify tests for the minimum and maximum number of bytes in the returned page. You may also specify tests for the minimum and maximum web server response time.
Data flow for HTTP::WebTest:
-------------- -------------
| | | |
| Input |------------->| WebTest |
| parameters | | |
| | -------------
-------------- | ^
| |
V |
------------- ------------
| | request | |
| Remote || user |
| | response | agent |
------------- | |
------------
<<lessSYNOPSIS
use HTTP::WebTest;
my $webtest = new HTTP::WebTest;
# run test from file
$webtest->run_wtscript(script.wt);
# or (to pass test parameters as method arguments)
$webtest->run_tests($tests);
Introduction
This module runs tests on remote URLs containing Perl/JSP/HTML/JavaScript/etc. and generates a detailed test report. This module can be used "as-is" or its functionality can be extended using plugins. Plugins can define test types and provide additional report capabilities. This module comes with a set of default plugins but can be easily extended with third party plugins.
The wt script is provided for running HTTP::WebTest from the command line.
The test specifications can be read from a parameter file in wtscript format or input as method arguments. The test results can be displayed on the terminal, directed to a file, stored in a scalar variable. The test results can also be emailed. The report can be modified and extended using report plugins.
Each URL/web file is tested by fetching it from the web server using a local instance of an HTTP user agent. The basic test is simply whether or not the fetch was successful. You may also test using literal strings or regular expressions that are either required to exist or forbidden to exist in the fetched page. You may also specify tests for the minimum and maximum number of bytes in the returned page. You may also specify tests for the minimum and maximum web server response time.
Data flow for HTTP::WebTest:
-------------- -------------
| | | |
| Input |------------->| WebTest |
| parameters | | |
| | -------------
-------------- | ^
| |
V |
------------- ------------
| | request | |
| Remote || user |
| | response | agent |
------------- | |
------------
Download (0.088MB)
Added: 2006-12-14 License: Perl Artistic License Price:
1044 downloads
HttpAuth 0.6
HttpAuth is a daemon and framework for authenticating HTTP requests. more>>
HttpAuth is a daemon and framework for authenticating HTTP requests. It supports Basic and Digest authentication against various databases such as LDAP, PostgreSQL, or MySQL.
HttpAuth project also supports NTLM authentication against a Windows Server.
Compatibility: Various web servers can talk with httpauthd. Currently modules, plugins or code for the following systems have been written:
- Apache 1.3.x
- Apache 2.x
- Java Servlets
- Jetty Web Server
Enhancements:
- A crash which occurred when doing some sort of Basic authentication was fixed.
- Numbers are now allowed in handler names.
- The program reconnects properly to httpauthd when that daemon has been restarted.
- The Java (Jetty) authenticator now supports NTLM properly.
- A bug where Apache 2.x wouldnt lock down credentials for NTLM properly to a single connection was fixed.
<<lessHttpAuth project also supports NTLM authentication against a Windows Server.
Compatibility: Various web servers can talk with httpauthd. Currently modules, plugins or code for the following systems have been written:
- Apache 1.3.x
- Apache 2.x
- Java Servlets
- Jetty Web Server
Enhancements:
- A crash which occurred when doing some sort of Basic authentication was fixed.
- Numbers are now allowed in handler names.
- The program reconnects properly to httpauthd when that daemon has been restarted.
- The Java (Jetty) authenticator now supports NTLM properly.
- A bug where Apache 2.x wouldnt lock down credentials for NTLM properly to a single connection was fixed.
Download (0.88MB)
Added: 2006-12-22 License: GPL (GNU General Public License) Price:
1037 downloads
Jifty::Request 0.60912
Jifty::Request is a canonical internal representation of an incoming Jifty request. more>>
Jifty::Request is a canonical internal representation of an incoming Jifty request.
This document discusses the ins and outs of getting data from the web browser (or any other source) and figuring out what it means. Most of the time, you wont need to worry about the details, but they are provided below if youre curious.
This class parses the submission and makes it available as a protocol-independent Jifty::Request object.
Each request contains several types of information:
actions
A request may contain one or more actions; these are represented as Jifty::Request::Action objects. Each action request has a moniker, a set of submitted arguments, and an implementation class. By default, all actions that are submitted are run; it is possible to only mark a subset of the submitted actions as "active", and only the active actions will be run. These will eventually become full-fledge Jifty::Action objects.
state variables
State variables are used to pass around bits of information which are needed more than once but not often enough to be stored in the session. Additionally, they are per-browser window, unlike session information.
continuations
Continuations can be called or created during the course of a request, though each request has at most one "current" continuation. See Jifty::Continuation.
(optional) fragments
Fragments are standalone bits of reusable code. They are most commonly used in the context of AJAX, where fragments are the building blocks that can be updated independently. A request is either for a full page, or for multiple independent fragments. See Jifty::Web::PageRegion.
<<lessThis document discusses the ins and outs of getting data from the web browser (or any other source) and figuring out what it means. Most of the time, you wont need to worry about the details, but they are provided below if youre curious.
This class parses the submission and makes it available as a protocol-independent Jifty::Request object.
Each request contains several types of information:
actions
A request may contain one or more actions; these are represented as Jifty::Request::Action objects. Each action request has a moniker, a set of submitted arguments, and an implementation class. By default, all actions that are submitted are run; it is possible to only mark a subset of the submitted actions as "active", and only the active actions will be run. These will eventually become full-fledge Jifty::Action objects.
state variables
State variables are used to pass around bits of information which are needed more than once but not often enough to be stored in the session. Additionally, they are per-browser window, unlike session information.
continuations
Continuations can be called or created during the course of a request, though each request has at most one "current" continuation. See Jifty::Continuation.
(optional) fragments
Fragments are standalone bits of reusable code. They are most commonly used in the context of AJAX, where fragments are the building blocks that can be updated independently. A request is either for a full page, or for multiple independent fragments. See Jifty::Web::PageRegion.
Download (0.52MB)
Added: 2006-10-20 License: Perl Artistic License Price:
1099 downloads
CGI::Request 2.0b1
CGI::Request is a parse client request via a CGI interface. more>>
CGI::Request is a parse client request via a CGI interface.
SYNOPSIS
use CGI::Request;
# Simple interface: (combines SendHeaders, new and import_names)
$req = GetRequest($pkg);
print FmtRequest(); # same as: print $req->as_string
# Full Interface:
$req = new CGI::Request; # fetch and parse request
$field_value = $req->param(FieldName);
@selected = $req->param(SelectMultiField);
@keywords = $req->keywords; # from ISINDEX
print $req->as_string; # format Form and CGI variables
# import form fields into a package as perl variables!
$req->import_names(R);
print "$R::FieldName";
print "@R::SelectMultiField";
@value = $req->param_or($fieldname, $default_return_value);
# Access to CGI interface (see CGI::Base)
$cgi_obj = $req->cgi;
$cgi_var = $req->cgi->var("REMOTE_ADDR");
# Other Functions:
CGI::Request::Interface($cgi); # specify alternative CGI
CGI::Request::Debug($level); # log to STDERR (see CGI::Base)
# Cgi-lib compatibility functions
# use CGI::Request qw(:DEFAULT :cgi-lib); to import them
&ReadParse(*input);
&MethGet;
&PrintHeader;
&PrintVariables(%input);
This module implements the CGI::Request object. This object represents a single query / request / submission from a WWW user. The CGI::Request class understands the concept of HTML forms and fields, specifically how to parse a CGI QUERY_STRING.
<<lessSYNOPSIS
use CGI::Request;
# Simple interface: (combines SendHeaders, new and import_names)
$req = GetRequest($pkg);
print FmtRequest(); # same as: print $req->as_string
# Full Interface:
$req = new CGI::Request; # fetch and parse request
$field_value = $req->param(FieldName);
@selected = $req->param(SelectMultiField);
@keywords = $req->keywords; # from ISINDEX
print $req->as_string; # format Form and CGI variables
# import form fields into a package as perl variables!
$req->import_names(R);
print "$R::FieldName";
print "@R::SelectMultiField";
@value = $req->param_or($fieldname, $default_return_value);
# Access to CGI interface (see CGI::Base)
$cgi_obj = $req->cgi;
$cgi_var = $req->cgi->var("REMOTE_ADDR");
# Other Functions:
CGI::Request::Interface($cgi); # specify alternative CGI
CGI::Request::Debug($level); # log to STDERR (see CGI::Base)
# Cgi-lib compatibility functions
# use CGI::Request qw(:DEFAULT :cgi-lib); to import them
&ReadParse(*input);
&MethGet;
&PrintHeader;
&PrintVariables(%input);
This module implements the CGI::Request object. This object represents a single query / request / submission from a WWW user. The CGI::Request class understands the concept of HTML forms and fields, specifically how to parse a CGI QUERY_STRING.
Download (0.12MB)
Added: 2006-10-21 License: Perl Artistic License Price:
1099 downloads
PITA::XML::Request 0.30
PITA::XML::Request is a request for the testing of a software package. more>>
PITA::XML::Request is a request for the testing of a software package.
SYNOPSIS
# Create a request specification
my $dist = PITA::XML::Request->new(
scheme => perl5,
distname => PITA-XML,
# The package to test
file => PITA::XML::File->new(
filename => Foo-Bar-0.01.tar.gz,
digest => MD5.0123456789ABCDEF0123456789ABCDEF,
),
# Optional fields for repository-based requests
authority => cpan,
authpath => /id/A/AD/ADAMK/Foo-Bar-0.01.tar.gz,
);
PITA::XML::Request is an object for holding information about a request for a distribution to be tested. It is created most often as part of the parsing of a PITA::XML XML file.
It holds the testing scheme, name of the distribition, file information, and authority information (if the distribution was sourced from a repository such as CPAN)
<<lessSYNOPSIS
# Create a request specification
my $dist = PITA::XML::Request->new(
scheme => perl5,
distname => PITA-XML,
# The package to test
file => PITA::XML::File->new(
filename => Foo-Bar-0.01.tar.gz,
digest => MD5.0123456789ABCDEF0123456789ABCDEF,
),
# Optional fields for repository-based requests
authority => cpan,
authpath => /id/A/AD/ADAMK/Foo-Bar-0.01.tar.gz,
);
PITA::XML::Request is an object for holding information about a request for a distribution to be tested. It is created most often as part of the parsing of a PITA::XML XML file.
It holds the testing scheme, name of the distribition, file information, and authority information (if the distribution was sourced from a repository such as CPAN)
Download (0.070MB)
Added: 2007-01-10 License: Perl Artistic License Price:
1017 downloads
Apache2::RequestRec 2.0.3
Apache2::RequestRec is a Perl API for Apache request record accessors. more>>
Apache2::RequestRec is a Perl API for Apache request record accessors.
Synopsis
use Apache2::RequestRec ();
# set supported by the handler HTTP methods
$allowed = $r->allowed();
# auth type
$auth_type = $r->ap_auth_type();
# QUERY_STRING
$args = $r->args();
# non-parsed-headers handler
$status = $r->assbackwards();
# how many bytes were sent
$bytes_sent = $r->bytes_sent();
# client connection record
$c = $r->connection();
# "Content-Encoding" HTTP response header
$r->content_encoding("gzip");
# the languages of the content
$languages = $r->content_languages();
# "Content-Encoding" HTTP response header
$r->content_type(text/plain);
# special response headers table
$err_headers_out = $r->err_headers_out();
# request mapped filename
$filename = $r->filename();
# request finfo
$finfo = $r->finfo();
# SetHandler perl-script equivalent
$r->handler(perl-script);
# was it a HEAD request?
$status = $r->header_only();
# request input headers table
$headers_in = $r->headers_in();
# request output headers table
$headers_out = $r->headers_out();
# hostname
$hostname = $r->hostname();
# input filters stack
$input_filters = $r->input_filters();
# get the main request obj in a sub-request
$main_r = $r->main();
# whats the current request (GET/POST/etc)?
$method = $r->method();
# whats the current method number?
$methnum = $r->method_number();
# current resource last modified time
$mtime = $r->mtime();
# next request object (in redirect)
$next_r = $r->next();
# there is no local copy
$r->no_local_copy();
# Apache ascii notes table
$notes = $r->notes();
# output filters stack
$output_filters = $r->output_filters();
# PATH_INFO
$path_info = $r->path_info();
# used in configuration directives modules
$per_dir_config = $r->per_dir_config();
# pool with life span of the current request
$p = $r->pool();
# previous request object in the internal redirect
$prev_r = $r->prev();
# connection level input filters stack
$proto_input_filters = $r->proto_input_filters();
# HTTP protocol version number
$proto_num = $r->proto_num();
# connection level output filters stack
$proto_output_filters = $r->proto_output_filters();
# the protocol, the client speaks: "HTTP/1.0", "HTTP/1.1", etc.
$protocol = $r->protocol();
# is it a proxy request
$status = $r->proxyreq($val);
# Time when the request started
$request_time = $r->request_time();
# server object
$s = $r->server();
# response status
$status = $r->status();
# response status line
$status_line = $r->status_line();
# manipulate %ENV of the subprocess
$r->subprocess_env;
$r->subprocess_env($key => $val);
# first HTTP request header
$request = $r->the_request();
# the URI without any parsing performed
$unparsed_uri = $r->unparsed_uri();
# The path portion of the URI
$uri = $r->uri();
# auth username
$user = $r->user();
<<lessSynopsis
use Apache2::RequestRec ();
# set supported by the handler HTTP methods
$allowed = $r->allowed();
# auth type
$auth_type = $r->ap_auth_type();
# QUERY_STRING
$args = $r->args();
# non-parsed-headers handler
$status = $r->assbackwards();
# how many bytes were sent
$bytes_sent = $r->bytes_sent();
# client connection record
$c = $r->connection();
# "Content-Encoding" HTTP response header
$r->content_encoding("gzip");
# the languages of the content
$languages = $r->content_languages();
# "Content-Encoding" HTTP response header
$r->content_type(text/plain);
# special response headers table
$err_headers_out = $r->err_headers_out();
# request mapped filename
$filename = $r->filename();
# request finfo
$finfo = $r->finfo();
# SetHandler perl-script equivalent
$r->handler(perl-script);
# was it a HEAD request?
$status = $r->header_only();
# request input headers table
$headers_in = $r->headers_in();
# request output headers table
$headers_out = $r->headers_out();
# hostname
$hostname = $r->hostname();
# input filters stack
$input_filters = $r->input_filters();
# get the main request obj in a sub-request
$main_r = $r->main();
# whats the current request (GET/POST/etc)?
$method = $r->method();
# whats the current method number?
$methnum = $r->method_number();
# current resource last modified time
$mtime = $r->mtime();
# next request object (in redirect)
$next_r = $r->next();
# there is no local copy
$r->no_local_copy();
# Apache ascii notes table
$notes = $r->notes();
# output filters stack
$output_filters = $r->output_filters();
# PATH_INFO
$path_info = $r->path_info();
# used in configuration directives modules
$per_dir_config = $r->per_dir_config();
# pool with life span of the current request
$p = $r->pool();
# previous request object in the internal redirect
$prev_r = $r->prev();
# connection level input filters stack
$proto_input_filters = $r->proto_input_filters();
# HTTP protocol version number
$proto_num = $r->proto_num();
# connection level output filters stack
$proto_output_filters = $r->proto_output_filters();
# the protocol, the client speaks: "HTTP/1.0", "HTTP/1.1", etc.
$protocol = $r->protocol();
# is it a proxy request
$status = $r->proxyreq($val);
# Time when the request started
$request_time = $r->request_time();
# server object
$s = $r->server();
# response status
$status = $r->status();
# response status line
$status_line = $r->status_line();
# manipulate %ENV of the subprocess
$r->subprocess_env;
$r->subprocess_env($key => $val);
# first HTTP request header
$request = $r->the_request();
# the URI without any parsing performed
$unparsed_uri = $r->unparsed_uri();
# The path portion of the URI
$uri = $r->uri();
# auth username
$user = $r->user();
Download (3.5MB)
Added: 2007-07-16 License: The Apache License 2.0 Price:
830 downloads
lns.http 0.1
lns.http is a simple framework for writing Common LISP Web applications. more>>
lns.http is a simple framework for writing Common Lisp web applications. The project handles the incoming connections, parses HTTP headers and queries, and finally hands control over to your URL handler.
lns.http is a HTTP/1.1 compatible web server but tries to achieve compatibility with lesser (down to the informal HTTP/0.9) clients.
The lns.http web server uses lisp-network-server to take care of network handling.
This software is licensed unter the LGPL.
<<lesslns.http is a HTTP/1.1 compatible web server but tries to achieve compatibility with lesser (down to the informal HTTP/0.9) clients.
The lns.http web server uses lisp-network-server to take care of network handling.
This software is licensed unter the LGPL.
Download (0.017MB)
Added: 2006-12-19 License: LGPL (GNU Lesser General Public License) Price:
1046 downloads
Change Control Request Manager 0.3.0
Change Control Request Manager is an online system for managing change requests for businesses. more>>
Change Control Request Manager is an online system for managing change requests for businesses. Change Control Request Manager project can be customized to fit the needs of a particular business.
Main features:
- Abillity to customize data entry fields. Field type include test, dropdown list, boolean, date, and integer.
- Search for existing CCR records.
- Custom logo. You can place your companys logo at the top.
- Custom Disclaimer message.
- User administration.
- Install script.
Enhancements:
- A reporting system was added.
- Similar to the browse order screen, you can customize the report and display a date range to print.
<<lessMain features:
- Abillity to customize data entry fields. Field type include test, dropdown list, boolean, date, and integer.
- Search for existing CCR records.
- Custom logo. You can place your companys logo at the top.
- Custom Disclaimer message.
- User administration.
- Install script.
Enhancements:
- A reporting system was added.
- Similar to the browse order screen, you can customize the report and display a date range to print.
Download (0.17MB)
Added: 2006-07-21 License: GPL (GNU General Public License) Price:
1193 downloads
HappyHTTP 0.1
HappyHTTP is a simple C++ library for issuing HTTP requests and processing responses. more>>
HappyHTTP is a simple C++ library for issuing HTTP requests and processing responses.
Main features:
- Simple to integrate - just drop in the .h and .cpp files
- Easy-to-use interface (example)
- Non-blocking operation, suitable for use in game update loops
- Supports pipelining. You can issue multiple requests without waiting for responses.
- Licensed under the zlib/libpng license.
- Cross-platform (Linux, OSX, Windows, at least)
Usage:
The interface is based loosely on Pythons httplib. Ive kept the same terminology where possible.
All HappyHTTP code is kept within the happyhttp namespace
To issue and process a HTTP request, the basic steps are:
- Create a connection object
- Set up callbacks for handling responses
- Issue request(s)
- pump the connection at regular intervals. As responses are received, the callbacks will be invoked.
<<lessMain features:
- Simple to integrate - just drop in the .h and .cpp files
- Easy-to-use interface (example)
- Non-blocking operation, suitable for use in game update loops
- Supports pipelining. You can issue multiple requests without waiting for responses.
- Licensed under the zlib/libpng license.
- Cross-platform (Linux, OSX, Windows, at least)
Usage:
The interface is based loosely on Pythons httplib. Ive kept the same terminology where possible.
All HappyHTTP code is kept within the happyhttp namespace
To issue and process a HTTP request, the basic steps are:
- Create a connection object
- Set up callbacks for handling responses
- Issue request(s)
- pump the connection at regular intervals. As responses are received, the callbacks will be invoked.
Download (0.013MB)
Added: 2006-05-10 License: zlib/libpng License Price:
1262 downloads
httping 1.2.4
httping is a ping-like tool for HTTP requests. more>>
httping is a "ping"-like tool for HTTP requests. Give it a URL and it will show how long it takes to connect, send a request, and retrieve the reply (only the headers).
httping can be used for monitoring or statistical purposes (measuring latency).
Enhancements:
- A big memory leak in the SSL code was fixed.
- An audible ping mode was added.
<<lesshttping can be used for monitoring or statistical purposes (measuring latency).
Enhancements:
- A big memory leak in the SSL code was fixed.
- An audible ping mode was added.
Download (0.008MB)
Added: 2007-07-10 License: GPL (GNU General Public License) Price:
841 downloads
HTTunnel 0.04
HTTunnel is a universal HTTP tunnel using Apache, mod_perl and Perl. more>>
HTTunnel is a universal HTTP tunnel using Apache, mod_perl and Perl.
To install this module do the following:
perl Makefile.PL
make
make test
make install
Note 1: The test suite will require the URL to an Apache::HTTunnel server to run. You will prompted for it during the installation. This server must allow tunnels to localhost:80. That Apache server must also return an HTTP 200 code for a "GET / HTTP/1.0" request.
Generally if the server has index.html file in the document root it will be ok.
<<lessTo install this module do the following:
perl Makefile.PL
make
make test
make install
Note 1: The test suite will require the URL to an Apache::HTTunnel server to run. You will prompted for it during the installation. This server must allow tunnels to localhost:80. That Apache server must also return an HTTP 200 code for a "GET / HTTP/1.0" request.
Generally if the server has index.html file in the document root it will be ok.
Download (0.011MB)
Added: 2006-07-03 License: Artistic License Price:
1209 downloads
HTTP::Browscap 0.02
HTTP::Browscap is a Perl module that can parse and search browscap.ini files. more>>
HTTP::Browscap is a Perl module that can parse and search browscap.ini files.
SYNOPSIS
use HTTP::Browscap;
my $capable = browscap();
if( $capable->{wap} ) {
output_WAP();
}
if( $capable->{css} > 1 ) {
# Browser can handle CSS2
}
# OO interface
my $BC = HTTP::Browscap->new( browscap.ini );
$capable = $BC->match( $ENV{HTTP_USER_AGENT} );
ABSTRACT
Browscap.ini is a file, introduced with Microsofts IIS, that lists the User-Agent strings that different browsers send, and various capabilities of those browsers. This module parses browscap.ini and allows you to find the capability definitions for a given browser.
Starting with Microsofts IIS, a browscap.ini file was used to list the capabilities of various browsers. Using the User-Agent string that a browser sends in the HTTP request, the capabilities of a browser are retrieved. If an exact match of the User-Agent string isnt found, wild-card expantion is done. If all fails, a default browser definition is used.
There are limits the usefulness of browscap.ini. It only detects if a browser has a certain capability, but not if this capability has been deactivated or if its a buggy implementation. In particular, most CSS and JavaScript implementations will make you scream.
<<lessSYNOPSIS
use HTTP::Browscap;
my $capable = browscap();
if( $capable->{wap} ) {
output_WAP();
}
if( $capable->{css} > 1 ) {
# Browser can handle CSS2
}
# OO interface
my $BC = HTTP::Browscap->new( browscap.ini );
$capable = $BC->match( $ENV{HTTP_USER_AGENT} );
ABSTRACT
Browscap.ini is a file, introduced with Microsofts IIS, that lists the User-Agent strings that different browsers send, and various capabilities of those browsers. This module parses browscap.ini and allows you to find the capability definitions for a given browser.
Starting with Microsofts IIS, a browscap.ini file was used to list the capabilities of various browsers. Using the User-Agent string that a browser sends in the HTTP request, the capabilities of a browser are retrieved. If an exact match of the User-Agent string isnt found, wild-card expantion is done. If all fails, a default browser definition is used.
There are limits the usefulness of browscap.ini. It only detects if a browser has a certain capability, but not if this capability has been deactivated or if its a buggy implementation. In particular, most CSS and JavaScript implementations will make you scream.
Download (0.009MB)
Added: 2007-06-09 License: Perl Artistic License Price:
875 downloads
Yahoo::Search::Request 1.7.10
Yahoo::Search::Request is a container object for a Yahoo! Search request. more>>
Yahoo::Search::Request is a container object for a Yahoo! Search request. (This package is included in, and automatically loaded by, the Yahoo::Search package.)
Package Use
You never need to use this package directly -- it is loaded automatically by Yahoo::Search.
Object Creation
In practice, this class is generally not dealt with explicitly, but rather implicitly via functions in Yahoo::Search such as Query and Links, which build and use a Request object under the hood.
You also have access to the Request object via Request() method of resulting Response and Result objects.
To be clear, Request objects are created by the Request() method of a Search Engine object (Yahoo::Search).
<<lessPackage Use
You never need to use this package directly -- it is loaded automatically by Yahoo::Search.
Object Creation
In practice, this class is generally not dealt with explicitly, but rather implicitly via functions in Yahoo::Search such as Query and Links, which build and use a Request object under the hood.
You also have access to the Request object via Request() method of resulting Response and Result objects.
To be clear, Request objects are created by the Request() method of a Search Engine object (Yahoo::Search).
Download (0.004MB)
Added: 2006-12-06 License: Perl Artistic License Price:
1052 downloads
Generic Apache Request Library 2.08
Generic Apache Request Libr is a shared library with associated modules for manipulating client request data via the Apache API. more>>
libapreq is a shared library with associated modules for manipulating client request data via the Apache API.
Generic Apache Request Library also includes language bindings for Perl (Apache::Request and Apache::Cookie). Functionality includes:
parsing of application/x-www-form-urlencoded data
parsing of multipart/form-data
parsing of HTTP cookies
Enhancements:
- This release adds some Perl/C API fixes and build improvements.
<<lessGeneric Apache Request Library also includes language bindings for Perl (Apache::Request and Apache::Cookie). Functionality includes:
parsing of application/x-www-form-urlencoded data
parsing of multipart/form-data
parsing of HTTP cookies
Enhancements:
- This release adds some Perl/C API fixes and build improvements.
Download (0.76MB)
Added: 2006-08-11 License: GPL (GNU General Public License) Price:
1169 downloads
HTTP::Handle 0.2
HTTP::Handle is a HTTP Class designed for streaming. more>>
HTTP::Handle is a HTTP Class designed for streaming.
SYNOPSIS
use HTTP::Handle;
my $http = HTTP::Handle->new( uri => "http://www.google.com/" );
$http->connect();
my $fd = $http->fd();
while () {
print "--> $_";
}
The HTTP::Handle module allows you to make HTTP requests and handle the data yourself. The general ideas is that you use this module to make a HTTP request and handle non-header data yourself. I needed such a feature for my mp3 player to listen to icecast streams.
HTTP::Handle->new()
Create a new HTTP::Handle object thingy.
Arguments possible:
url => "http://www.google.com/"
Sets the initial URL to connect to.
follow_redirects => [ 0 | 1 ]
Automatically follow HTTP redirects. This defaults to true (1). Set to 0 to disable this.
http_request => HASHREF
Any thing put in here will be sent as "key: value" in the http request string.
$http->connect()
Connect, send the http request, and process the response headers.
This function returns -1 on failure, undef otherwise. The reason for failure will be printed to STDERR.
$http->fd()
Get the file descriptor (socket) were using to connect.
$http->url( [ url_string ])
Get or set the URL. If a url string is passed, you will change the url that is requested. If no parameter is passed, a URI object will be returned containing the
$http->follow_redirects( [ 0 | 1 ] )
If a value is passed then you will set whether or not we will automatically follow HTTP 302 Redirects. If no value is passed, then we will return whatever the current option is.
Defaults to 1 (will follow redirects).
$http->http_request_string()
Returns a string containing the HTTP request and headers, this is used when
$http->connect() is called.
<<lessSYNOPSIS
use HTTP::Handle;
my $http = HTTP::Handle->new( uri => "http://www.google.com/" );
$http->connect();
my $fd = $http->fd();
while () {
print "--> $_";
}
The HTTP::Handle module allows you to make HTTP requests and handle the data yourself. The general ideas is that you use this module to make a HTTP request and handle non-header data yourself. I needed such a feature for my mp3 player to listen to icecast streams.
HTTP::Handle->new()
Create a new HTTP::Handle object thingy.
Arguments possible:
url => "http://www.google.com/"
Sets the initial URL to connect to.
follow_redirects => [ 0 | 1 ]
Automatically follow HTTP redirects. This defaults to true (1). Set to 0 to disable this.
http_request => HASHREF
Any thing put in here will be sent as "key: value" in the http request string.
$http->connect()
Connect, send the http request, and process the response headers.
This function returns -1 on failure, undef otherwise. The reason for failure will be printed to STDERR.
$http->fd()
Get the file descriptor (socket) were using to connect.
$http->url( [ url_string ])
Get or set the URL. If a url string is passed, you will change the url that is requested. If no parameter is passed, a URI object will be returned containing the
$http->follow_redirects( [ 0 | 1 ] )
If a value is passed then you will set whether or not we will automatically follow HTTP 302 Redirects. If no value is passed, then we will return whatever the current option is.
Defaults to 1 (will follow redirects).
$http->http_request_string()
Returns a string containing the HTTP request and headers, this is used when
$http->connect() is called.
Download (0.005MB)
Added: 2006-11-16 License: Perl Artistic License Price:
1072 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above http request search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed