| URI - Uniform Resource Identifiers |
URI - Uniform Resource Identifiers (absolute and relative)
use URI;
$u1 = URI->new("http://www.perl.com";);
$u2 = URI->new("foo", "http");
$u3 = $u2->abs($u1);
$u4 = $u3->clone;
$u5 = URI->new("HTTP://WWW.perl.com:80";)->canonical;
$str = $u->as_string; $str = "$u";
$scheme = $u->scheme; $opaque = $u->opaque; $path = $u->path; $frag = $u->fragment;
$u->scheme("ftp");
$u->host("ftp.perl.com");
$u->path("cpan/");
This module implements the URI class. Objects of this class
represent ``Uniform Resource Identifier references'' as specified in RFC
2396 (and updated by RFC 2732).
A Uniform Resource Identifier is a compact string of characters that
identifies an abstract or physical resource. A Uniform Resource
Identifier can be further classified as either a Uniform Resource Locator
(URL) or a Uniform Resource Name (URN). The distinction between URL
and URN does not matter to the URI class interface. A
``URI-reference'' is a URI that may have additional information attached
in the form of a fragment identifier.
An absolute URI reference consists of three parts: a scheme, a scheme-specific part and a fragment identifier. A subset of URI references share a common syntax for hierarchical namespaces. For these, the scheme-specific part is further broken down into authority, path and query components. These URIs can also take the form of relative URI references, where the scheme (and usually also the authority) component is missing, but implied by the context of the URI reference. The three forms of URI reference syntax are summarized as follows:
<scheme>:<scheme-specific-part>#<fragment> <scheme>://<authority><path>?<query>#<fragment> <path>?<query>#<fragment>
The components into which a URI reference can be divided depend on the
scheme. The URI class provides methods to get and set the
individual components. The methods available for a specific
URI object depend on the scheme.
The following methods construct new URI objects:
The constructor determines the scheme, maps this to an appropriate URI subclass, constructs a new object of that class and returns it.
If the scheme isn't one of those that URI recognizes, you still get
an URI object back that you can access the generic methods on. The
$uri->has_recognized_scheme method can be used to test for
this.
The $scheme argument is only used when $str is a
relative URI. It can be either a simple string that
denotes the scheme, a string containing an absolute URI reference, or
an absolute URI object. If no $scheme is specified for a relative
URI $str, then $str is simply treated as a generic URI (no scheme-specific
methods available).
The set of characters available for building URI references is restricted (see the URI::Escape manpage). Characters outside this set are automatically escaped by the URI constructor.
The methods described in this section are available for all URI
objects.
Methods that give access to components of a URI always return the
old value of the component. The value returned is undef if the
component was not present. There is generally a difference between a
component that is empty (represented as "") and a component that is
missing (represented as undef). If an accessor method is given an
argument, it updates the corresponding component in addition to
returning the old value of the component. Passing an undefined
argument removes the component (if possible). The description of
each accessor method indicates whether the component is passed as
an escaped (percent-encoded) or an unescaped string. A component that can be further
divided into sub-parts are usually passed escaped, as unescaping might
change its semantics.
The common methods available for all URI are:
undef. If called with an
argument, it updates the scheme of $uri, possibly changing the
class of $uri, and returns the old scheme value. The method croaks
if the new scheme name is illegal; a scheme name must begin with a
letter and must consist of only US-ASCII letters, numbers, and a few
special marks: ``.'', ``+'', ``-''. This restriction effectively means
that the scheme must be passed unescaped. Passing an undefined
argument to the scheme method makes the URI relative (if possible).
Letter case does not matter for scheme names. The string returned by $uri->scheme is always lowercase. If you want the scheme just as it was written in the URI in its original case, you can use the $uri->_scheme method instead.
It will also be TRUE for relative URLs where a recognized
scheme was provided to the constructor, even if $uri->scheme
returns undef for these.
For efficiency reasons, if the $uri is already in normalized form, then a reference to it is returned instead of a copy.
If you need to test whether two URI object references denote the
same object, use the '==' operator.
The following methods are available to schemes that use the common/generic syntax for hierarchical namespaces. The descriptions of schemes below indicate which these are. Unrecognized schemes are assumed to support the generic syntax, and therefore the following methods:
Note that absolute paths have the empty string as their first
path_segment, i.e. the path /foo/bar have 3
path_segments; ``'', ``foo'' and ``bar''.
The form can be set either by passing separate key/value pairs, or via an array or hash reference. Passing an empty array or an empty hash removes the query component, whereas passing no arguments at all leaves the component unchanged. The order of keys is undefined if a hash reference is passed. The old value is always returned as a list of separate key/value pairs. Assigning this list to a hash is unwise as the keys returned might repeat.
The values passed when setting the form can be plain strings or references to arrays of strings. Passing an array of values has the same effect as passing the key repeatedly with one value at a time. All the following statements have the same effect:
$uri->query_form(foo => 1, foo => 2);
$uri->query_form(foo => [1, 2]);
$uri->query_form([ foo => 1, foo => 2 ]);
$uri->query_form([ foo => [1, 2] ]);
$uri->query_form({ foo => [1, 2] });
The $delim parameter can be passed as ``;'' to force the key/value pairs to be delimited by ``;'' instead of ``&'' in the query string. This practice is often recommended for URLs embedded in HTML or XML documents as this avoids the trouble of escaping the ``&'' character. You might also set the $URI::DEFAULT_QUERY_FORM_DELIMITER variable to ``;'' for the same global effect.
The URI::QueryParam module can be loaded to add further methods to
manipulate the form of a URI. See the URI::QueryParam manpage for details.
The keywords can be set either by passing separate keywords directly or by passing a reference to an array of keywords. Passing an empty array removes the query component, whereas passing no arguments at all leaves the component unchanged. The old value is always returned as a list of separate words.
For schemes where the authority component denotes an Internet host, the following methods are available in addition to the generic methods.
For some schemes this is a user name and a password separated by a colon. This practice is not recommended. Embedding passwords in clear text (such as URI) has proven to be a security risk in almost every case where it has been used.
If the $new_host string ends with a colon and a number, then this number also sets the port.
For IPv6 addresses the brackets around the raw address is removed in the return value from $uri->host. When setting the host attribute to an IPv6 address you can use a raw address or one enclosed in brackets. The address needs to be enclosed in brackets if you want to pass in a new port value as well.
If a port is not specified explicitly in the URI, then the URI scheme's default port is returned. If you don't want the default port substituted, then you can use the $uri->_port method instead.
For IPv6 addresses the bracketing is preserved; thus URI->new(``http://[::1]/'')->host_port returns ``[::1]:80''. Contrast this with $uri->host which will remove the brackets.
Scheme-specific support is provided for the following URI schemes. For URI
objects that do not belong to one of these, you can only use the common and
generic methods.
URI objects belonging to the data scheme support the common methods
and two new methods to access their scheme-specific components:
$uri->media_type and $uri->data. See the URI::data manpage for details.
URI objects belonging to the file scheme support the common and
generic methods. In addition, they provide two methods for mapping file URIs
back to local file names; $uri->file and $uri->dir. See the URI::file manpage
for details.
URI objects belonging to the ftp scheme support the common,
generic and server methods. In addition, they provide two methods for
accessing the userinfo sub-components: $uri->user and $uri->password.
URI objects belonging to the gopher scheme support the common,
generic and server methods. In addition, they support some methods for
accessing gopher-specific path components: $uri->gopher_type,
$uri->selector, $uri->search, $uri->string.
URI objects belonging to the http scheme support the common,
generic and server methods.
URI objects belonging to the ldap scheme support the common,
generic and server methods as well as ldap-specific methods: $uri->dn,
$uri->attributes, $uri->scope, $uri->filter, $uri->extensions. See
the URI::ldap manpage for details.
URI objects belonging to the mailto scheme support the common
methods and the generic query methods. In addition, they support the
following mailto-specific methods: $uri->to, $uri->headers.
Note that the ``foo@example.com'' part of a mailto is not the
userinfo and host but instead the path. This allows a
mailto URI to contain multiple comma separated email addresses.
URI objects belonging to the mms scheme support the common,
generic, and server methods, with the exception of userinfo and
query-related sub-components.
URI objects belonging to the news scheme support the common,
generic and server methods. In addition, they provide some methods to
access the path: $uri->group and $uri->message.
URI objects belonging to the pop scheme support the common, generic
and server methods. In addition, they provide two methods to access the
userinfo components: $uri->user and $uri->auth
URI objects belonging to the rlogin scheme support the
common, generic and server methods.
URI objects belonging to the rtsp scheme support the common,
generic, and server methods, with the exception of userinfo and
query-related sub-components.
URI objects belonging to the rsync scheme support the common,
generic and server methods. In addition, they provide methods to
access the userinfo sub-components: $uri->user and $uri->password.
URI objects belonging to the sip scheme support the
common, generic, and server methods with the exception of path related
sub-components. In addition, they provide two methods to get and set
sip parameters: $uri->params_form and $uri->params.
URI objects belonging to the telnet scheme support the
common, generic and server methods.
URI objects belonging to the tn3270 scheme support the
common, generic and server methods.
URI objects belonging to the ssh scheme support the common,
generic and server methods. In addition, they provide methods to
access the userinfo sub-components: $uri->user and $uri->password.
URI objects belonging to the sftp scheme support the common,
generic and server methods. In addition, they provide methods to
access the userinfo sub-components: $uri->user and $uri->password.
URI
objects belonging to the urn scheme provide the common methods, and also the
methods $uri->nid and $uri->nss, which return the Namespace Identifier
and the Namespace-Specific String respectively.
The Namespace Identifier basically works like the Scheme identifier of URIs, and further divides the URN namespace. Namespace Identifier assignments are maintained at http://www.iana.org/assignments/urn-namespaces.
Letter case is not significant for the Namespace Identifier. It is always returned in lower case by the $uri->nid method. The $uri->_nid method can be used if you want it in its original case.
urn:isbn: namespace contains International Standard Book
Numbers (ISBNs) and is described in RFC 3187. A URI object belonging
to this namespace has the following extra methods (if the
Business::ISBN module is available): $uri->isbn,
$uri->isbn_publisher_code, $uri->isbn_group_code (formerly isbn_country_code,
which is still supported by issues a deprecation warning), $uri->isbn_as_ean.
urn:oid: namespace contains Object Identifiers (OIDs) and is
described in RFC 3061. An object identifier consists of sequences of digits
separated by dots. A URI object belonging to this namespace has an
additional method called $uri->oid that can be used to get/set the oid
value. In a list context, oid numbers are returned as separate elements.
The following configuration variables influence how the class and its methods behave:
URI->new("http:foo";)->abs("http://host/a/b";)
==> "http:foo";
local $URI::ABS_ALLOW_RELATIVE_SCHEME = 1;
URI->new("http:foo";)->abs("http://host/a/b";)
==> "http:/host/a/foo";
abs() method ignore excess ``..''
segments in the relative URI by setting $URI::ABS_REMOTE_LEADING_DOTS
to a TRUE value. The difference is demonstrated by the following
examples:
URI->new("../../../foo")->abs("http://host/a/b";)
==> "http://host/../../foo";
local $URI::ABS_REMOTE_LEADING_DOTS = 1;
URI->new("../../../foo")->abs("http://host/a/b";)
==> "http://host/foo";
key=value pairs
delimited by ``;'' instead of ``&'' which is the default.
There are some things that are not quite right:
/(...)/ || die;
$u->query("$1");
The escaping (percent encoding) of chars in the 128 .. 255 range passed to the
URI constructor or when setting URI parts using the accessor methods depend on
the state of the internal UTF8 flag (see utf8::is_utf8) of the string passed.
If the UTF8 flag is set the UTF-8 encoded version of the character is percent
encoded. If the UTF8 flag isn't set the Latin-1 version (byte) of the
character is percent encoded. This basically exposes the internal encoding of
Perl strings.
As an alternative to this module, the following (official) regular expression can be used to decode a URI:
my($scheme, $authority, $path, $query, $fragment) = $uri =~ m|(?:([^:/?#]+):)?(?://([^/?#]*))?([^?#]*)(?:\?([^#]*))?(?:#(.*))?|;
The URI::Split module provides the function uri_split() as a
readable alternative.
the URI::file manpage, the URI::WithBase manpage, the URI::QueryParam manpage, the URI::Escape manpage, the URI::Split manpage, the URI::Heuristic manpage
RFC 2396: ``Uniform Resource Identifiers (URI): Generic Syntax'', Berners-Lee, Fielding, Masinter, August 1998.
http://www.iana.org/assignments/uri-schemes
http://www.iana.org/assignments/urn-namespaces
Copyright 1995-2009 Gisle Aas.
Copyright 1995 Martijn Koster.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
This module is based on the URI::URL module, which in turn was
(distantly) based on the wwwurl.pl code in the libwww-perl for
perl4 developed by Roy Fielding, as part of the Arcadia project at the
University of California, Irvine, with contributions from Brooks
Cutter.
URI::URL was developed by Gisle Aas, Tim Bunce, Roy Fielding and
Martijn Koster with input from other people on the libwww-perl mailing
list.
URI and related subclasses was developed by Gisle Aas.
| URI - Uniform Resource Identifiers |