Free requested url software for linux

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.

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.

CGI::SecureState is a transparent, secure statefulness for CGI programs.

SYNOPSIS

use CGI::SecureState;

my @memory = qw(param1 param2 other_params_to_remember);
my $cgi = new CGI::SecureState(-stateDir => "states",
-mindSet => forgetful,
-memory => @memory);

print $cgi->header(), $cgi->start_html;
my $url = $cgi->state_url();
my $param = $cgi->state_param();
print I am a stateful CGI session.";
printI am a different ",
"script that also has access to this session.quot;;

Very Important Note for Users of CGI::SecureState 0.2x

For those still using the 0.2x series, CGI::SecureState changed enormously between 0.26 and 0.30. Specifically, the addition of mindsets is so important that if you run your old scripts unchanged under CGI::SecureState 0.3x, you will receive nasty warnings (likely both in output web pages and your log files) that will tell you not to do so. Please do yourself a favor by re-reading this documentation, as this mysterious mindset business (as well as all the scrumptious new features) will be made clear.

Of course, any and all comments on the changes are welcome. If you are interested, send mail to behroozi@cpan.org with the subject "CGI::SecureState Comment".

A Better Solution to the stateless problem.

HTTP is by nature a stateless protocol; as soon as the requested object is delivered, HTTP severs the objects connection to the client. HTTP retains no memory of the request details and does not relate subsequent requests with what it has already served.

There are a few methods available to deal with this problem, including forms and cookies, but most have problems themselves, including security issues (cookie stealing), browser support (cookie blocking), and painful implementations (forms).

CGI::SecureState solves this problem by storing session data in an encrypted state file on the server. CGI::SecureState is similar in purpose to CGI::Persistent (and retains much of the same user interface) but has a completely different implementation. For those of you who have worked with CGI::Persistent before, you will be pleased to learn that CGI::SecureState was designed to work with Perls taint mode and has worked flawlessly with mod_perl and Apache::Registry for over two years. CGI::SecureState was also designed from the ground up for security, a fact which may rear its ugly head if anybody tries to do something tricksy.

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).

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.

WWW::Google::SiteMap::URL is URL Helper class for WWW::Google::SiteMap.

This is a helper class that supports WWW::Google::SiteMap and WWW::Google::SiteMap::Index.

METHODS

new()

loc()

Change the URL associated with this object. For a WWW::Google::SiteMap this specifies the URL to add to the sitemap, for a WWW::Google::SiteMap::Index, this is the URL to the sitemap.

changefreq()

Set the change frequency of the object. This field is not used in sitemap indexes, only in sitemaps.

lastmod()

Set the last modified time. You have to provide this as one of the following:

a complete ISO8601 time string

A complete time string will be accepted in exactly this format:

YYYY-MM-DDTHH:MM:SS+TZ:TZ
YYYY - 4-digit year
MM - 2-digit month (zero padded)
DD - 2-digit year (zero padded)
T - literal character T
HH - 2-digit hour (24-hour, zero padded)
SS - 2-digit second (zero padded)
+TZ:TZ - Timezone offset (hours and minutes from GMT, 2-digit, zero padded)

epoch time

Seconds since the epoch, such as would be returned from time(). If you provide an epoch time, then an appropriate ISO8601 time will be constructed with gmtime() (which means the timezone offset will be +00:00). If anyone knows of a way to determine the timezone offset of the current host that is cross-platform and doesnt add dozens of dependencies then I might change this.
an ISO8601 date (YYYY-MM-DD)

A simple date in YYYY-MM-DD format. The time will be set to 00:00:00+00:00.

a DateTime object.

If a DateTime object is provided, then an appropriate timestamp will be constructed from it.

a HTTP::Response object.

If given an HTTP::Response object, the last modified time will be calculated from whatever time information is available in the response headers. Currently this means either the Last-Modified header, or tue current time - the current_age() calculated by the response object. This is useful for building web crawlers.

Note that in order to conserve memory, any of these items that you provide will be converted to a complete ISO8601 time string when they are stored. This means that if you pass an object to lastmod(), you cant get it back out. If anyone actually has a need to get the objects back out, then I might make a configuration option to store the objects internally.

If you have suggestions for other types of date/time objects or formats that would be usefule, let me know and Ill consider them.

priority()

Set the priority. This field is not used in sitemap indexes, only in sitemaps.

delete()

Delete this object from the sitemap or the sitemap index.

lenient()

If lenient contains a true value, then errors will not be fatal.

mod_urlscheme is an Apache 1.3/2.0/2.2 module that allows the Apache configuration author control over the scheme to use when constructing self-referential URLs.
Please note that this module is different from mod_scheme, which embeds the Tinyscheme interpreter into Apache. You can find that module here. I changed the name from mod_scheme to mod_urlscheme to avoid confusion.
The original module was only written to work on Apache 2.0. There is now also a version for Apache 1.3 + EAPI, although it wont work with stock 1.3. Please see the "Apache 1.3" section at the bottom of this page for details. The 2.0 module will work almost unchanged on Apache 2.2. There is a small naming change in the API that requires a slightly different version.
In several situations, Apache will attempt to construct a URL that will point to itself and will deliver the result to the client. The most notable occasion for this is when Apache is constructing a client redirect. This can for example happen when the client requests a URL that maps to a directory but doesnt include a trailing slash: Apache will send back a redirect to the same URL, but with a trailing slash appended. Other occasions include Redirect directives in the Apache configuration, or mod_proxy rewriting redirects coming from a backend server (when mod_proxy is functioning as a reverse proxy).
A self-referential URL has four distinct major components: the scheme, the hostname, the port number and the request URI, the latter including perhaps a query string and a fragment identifier. The combination of ServerName, UseCanonicalName and the use of the clients HTTP Host header allows an Apache administrator full control over the hostname and port number part of the generated URLs, but the scheme is up to Apache itself.
Normally, the scheme is always "http". A module such as mod_ssl will override this and set the scheme to "https" for those locations where it is active. But that doesnt help you when the Apache server is behind another server that will handle the HTTPS traffic for you. Imagine the following layered approach:
- The clients HTTPS request comes in to the first machine on port 443 (the default port for HTTPS). The first machine, which perhaps has dedicated hardware to speed up SSL processing, accepts the connection and provides for all the encryption/decryption. It forwards the decrypted request as a regular HTTP request to port 81 on the next machine.
- The second machine runs Apache. It will be listening on ports 80 and 81. It will receive the request from the first machine on port 81. The fact that its coming in on that port establishes the request as being secure, and Apache may provide different processing rules depending on whether the request is secure or not. (Of course, the Apache server should be behind a firewall, so a client cant connect to port 81 directly and circumvent the access controls.)
Now, if Apache for some reason needs to generate a redirect, the scheme on the redirect URL will be "http", because thats what Apache is serving. But that URL isnt valid on the outside: the scheme should be "https", so that the client will proceed to get the new URL from the same secure location.
One solution is to let the machine that handles the SSL work do the rewrite from http://www.example.com:81/ to https://www.example.com/. But that doesnt help you if the first machine is (for example) a dumb SSL tunnel that doesnt understand HTTP. In that case, Apache will need to be convinced its scheme is actually "https", not "http".
Thats where mod_urlscheme comes in.
Installation:
These instructions assume a Unix installation. For other systems, please consult the Apache documentation. mod_urlscheme is a very simple module that requires no special treatment. Simply put, if you can build mod_example from the stock Apache tree, then you can build mod_urlscheme as well.
Put the downloaded mod_urlscheme.c file in a temporary directory somewhere where you will compile it.
If you want to include mod_urlscheme as a static module in your Apache server, prepare your Apache source directory as per the Apache build instructions. When calling the ./configure command, include the option --with-module=experimental:/path/to/mod_urlscheme.c (for Apache 1.3: --add-module=/path/to/mod_urlscheme.c). You need to specify the full path to the source file after the colon. Then, proceed with the build instructions as you would normally. The module will be included in your Apache binary as a static module.
For a dynamic module, first install a full Apache distribution, including the apxs tool and the C headers. If you install from pre-packaged bundles, such as RPMs, you may need to separately install the development package. On RPM-based systems that usually means you need to have the httpd-devel package installed. You will also need a fully functional compiler suite installed.
Go to the directory where you put the mod_urlscheme.c file and run apxs -c mod_urlscheme.c. Refer to the Apache documentation to see if you need to specify more command line options for your system.
If the compile succeeded, you will now have a dynamic Apache module ready to use. You may need to look in the .libs subdirectory to find the actual mod_urlscheme.so file (under Unix, that is). Copy the module to the Apache module directory, which is the modules subdirectory of the server root (for Apache 1.3: the libexec subdirectory). Alternatively, you can put it in any other location; just make a note of where you put it, so you can refer to the location later on.

Redirection Tool is a product for Plone used for storing references to moved content to enable redirects.
The Redirection Tool can be used for storing references to moved content to enable redirects, or it can be used for giving objects multiple URLs (aliases). If a page is not found, the tool looks at its list of redirects to see if there is a match, and if so, it redirects to that page.
Future plans include a more intelligent 404 handling, where the tool would either search for alternative pages based on the components of the requested URL and automatically redirect if there is only one hit, otherwise display a limited number of hits, or alternatively chop off URL components until it finds an object that can be published to the user.
Enhancements:
- Added Plone 2.1 compatibility.