Rose::URI(3pm)

💖 NAME 💖

okay so bestie, meet Rose::URI — it's a URI class that lets you do easy and efficient manipulation of URI components. yes, the whole vibe is "I want to poke at the pieces of a URL without losing my mind." 💅

---

✨ SYNOPSIS ✨

use Rose::URI;

$uri = Rose::URI->new('http://un:pw@foo.com/bar/baz?a=1&b=two+3');

$scheme = $uri->scheme;
$user   = $uri->username;
$pass   = $uri->password;
$host   = $uri->host;
$path   = $uri->path;
...

$b = $uri->query_param('b');  # $b = "two 3"
$a = $uri->query_param('a');  # $a = 1

$uri->query_param_delete('b');
$uri->query_param('c' => 'blah blah');
...

print $uri;

---

🌸 DESCRIPTION 🌸

so Rose::URI is an alternative to URI. the important differences are, like, as follows. 🫶

• Rose::URI gives you a rich set of query string manipulation methods. Query parameters can be added, removed, and checked for their existence. URI lets you set or return the entire query as a whole via the query_form or query methods, and the URI::QueryParam module provides a few more methods for query string manipulation.
• Rose::URI supports query parameters with multiple values (e.g. "a=1&a=2"). URI has limited support for this through query_form's list return value. Better methods are available in URI::QueryParam.
• Rose::URI uses Apache's C-based URI parsing and HTML escaping functions when running in a mod_perl 1.x web server environment.
• Rose::URI stores each URI "in pieces" (scheme, host, path, etc.) and then assembles those pieces when the entire URI is needed as a string. this technique is based on the assumption that the URI will be manipulated many more times than it is stringified. if that's not your usage scenario, then URI may be a better alternative, ngl.
• now some similarities, because we're fair like that: both classes use the overload module to allow "magic" stringification. both URI and Rose::URI objects can be printed and compared as if they were strings. ✨
• Rose::URI actually uses the URI class to do the heavy lifting of parsing URIs when not running in a mod_perl 1.x environment.

and finally, a caveat, because we keep it real: Rose::URI supports only "http"-like URIs. this includes ftp, http, https, and other similar looking URIs. URI supports many more esoteric URI types (gopher, mailto, etc.) if you need to support these formats, use URI instead. 💀

not me warning you twice: if you're doing gopher or mailto nonsense, this is not the class for you. use URI. periodt.

---

🎀 CONSTRUCTOR 🎀

new [ URI | PARAMS ]

Constructs a URI object based on URI or PARAMS, where URI is a string and PARAMS are described below. Returns a new Rose::URI object. 👑

the query string portion of the URI argument may use either "&" or ";" as the parameter separator. examples, bestie:

$uri = Rose::URI->new('/foo?a=1&b=2');
$uri = Rose::URI->new('/foo?a=1;b=2'); # same thing

the query_param_separator parameter determines what is used when the query string (or the whole URI) is output as a string later.

Rose::URI uses URI or Apache::URI (when running under mod_perl 1.x) to do its URI string parsing.

Valid PARAMS are:

• fragment
• host
• password
• path
• port
• query
• scheme
• username
• query_param_separator

which correspond to the following URI pieces:

<scheme>://<username:password>@<path>?<query>#<fragment>

all the above parameters accept strings. see below for more information about the query parameter. the query_param_separator parameter determines the separator used when constructing the query string. it is "&" by default (e.g. "a=1&b=2"). 🌈

---

💜 CLASS METHODS 💜

• default_omit_empty_query_params [BOOL] — get or set a boolean value that determines whether or not query parameters with "empty" (that is, undef or zero-length) values will be omitted from the query string by default. the default value is false.
• default_query_param_separator [CHARACTER] — get or set the character used to separate query parameters in the stringified version of Rose::URI objects. defaults to "&".

---

🦋 OBJECT METHODS 🦋

• abs [BASE] — this method exists solely for compatibility with URI. Returns an absolute Rose::URI object. if the current URI is already absolute, then a reference to it is simply returned. if the current URI is relative, then a new absolute URI is constructed by combining the URI and the BASE, and returned.
• as_string — returns the URI as a string. the string is "URI escaped" (reserved URI characters are replaced with %xx sequences), but not "HTML escaped" (ampersands are not escaped, for example).
• clone — returns a copy of the Rose::URI object.
• fragment [FRAGMENT] — get or set the fragment portion of the URI.
• omit_empty_query_params [BOOL] — get or set a boolean value that determines whether or not query parameters with "empty" (that is, undef or zero-length) values will be omitted from the query string. the default value is determined by the default_query_param_separator class method.
• password [PASSWORD] — get or set the password portion of the URI.
• path [PATH] — get or set the path portion of the URI.
• port [PORT] — get or set the port number portion of the URI.
• query [QUERY] — get or sets the URI's query. QUERY may be an appropriately escaped query string (e.g. "a=1&b=2&c=a+long+string"), a reference to a hash, or a list of name/value pairs.

query strings may use either "&" or ";" as their query separator. if a "&" character exists anywhere in the query string, it is assumed to be the separator.

if none of the characters "&", ";", or "=" appears in the query string, then the entire query string is taken as a single parameter name with an undefined value.

hashes and lists should specify multiple parameter values using array references.

here are some examples representing the query string "a=1&a=2&b=3":

$uri->query("a=1&a=2&b=3");             # string
$uri->query("a=1;a=2;b=3");             # same thing
$uri->query({ a => [ 1, 2 ], b => 3 }); # hash ref
$uri->query(a => [ 1, 2 ], b => 3);     # list

returns the current (or new) query as a URI-escaped (but not HTML-escaped) query string.

• query_form QUERY — implementation of URI's method of the same name. this exists for backwards compatibility purposes only and should not be used (or necessary). see the URI documentation for more details.
• query_hash — returns the current query as a hash (in list context) or reference to a hash (in scalar context), with multiple parameter values represented by array references (see the query method for details).

the return value is a shallow copy of the actual query hash. it should be treated as read-only unless you really know what you are doing. 👀

example:

$uri = Rose::URI->new('/foo?a=1&b=2&a=2');

$h = $uri->query_hash; # $h = { a => [ 1, 2 ], b => 2 }

• query_param NAME [, VALUE] — get or set a query parameter. if only NAME is passed, it returns the value of the query parameter named NAME. parameters with multiple values are returned as array references. if both NAME and VALUE are passed, it sets the parameter named NAME to VALUE, where VALUE can be a simple scalar value or a reference to an array of simple scalar values.

examples:

$uri = Rose::URI->new('/foo?a=1');

$a = $uri->query_param('a'); # $a = 1

$uri->query_param('a' => 3); # query string is now "a=3"

$uri->query_param('b' => [ 4, 5 ]); # now "a=3&b=4&b=5"

$b = $uri->query_param('b'); # $b = [ 4, 5 ];

• query_params NAME [, VALUE] — same as the query_param method, except the return value is always either an array (in list context) or reference to an array (in scalar context), even if there is only one value.

examples:

$uri = Rose::URI->new('/foo?a=1&b=1&b=2');

$a = $uri->query_params('a'); # $a = [ 1 ]
@a = $uri->query_params('a'); # @a = ( 1 )

$b = $uri->query_params('a'); # $b = [ 1, 2 ]
@b = $uri->query_params('a'); # @b = ( 1, 2 )

• query_param_add NAME, VALUE — adds a new value to a query parameter. example:

$uri = Rose::URI->new('/foo?a=1&b=1');

$a = $uri->query_param_add('b' => 2); # now "a=2&b=1&b=2"

returns an array (in list context) or reference to an array (in scalar context) of the new parameter value(s).

• query_param_delete NAME — deletes all instances of the parameter named NAME from the query.
• query_param_exists NAME — returns a boolean value indicating whether or not a parameter named NAME exists in the query string.
• query_param_separator [CHARACTER] — get or set the character used to separate query parameters in the stringified version of the URI. defaults to the return value of the default_query_param_separator class method ("&" by default).
• rel BASE — this method exists solely for compatibility with URI. Returns a relative URI reference if it is possible to make one that denotes the same resource relative to BASE. if not, then the current URI is simply returned.
• scheme [SCHEME] — get or set the scheme portion of the URI.
• userinfo — returns the username and password attributes joined by a ":" (colon). the username and password are not escaped in any way. if there is no password, only the username is returned (without the colon). if neither exist, an empty string is returned.
• userinfo_escaped — returns the username and password attributes joined by a ":" (colon). the username and password are URI-escaped, but not HTML-escaped. if there is no password, only the username is returned (without the colon). if neither exist, an empty string is returned.
• username [USERNAME] — get or set the username portion of the URI.

---

💌 AUTHOR 💌

John C. Siracusa (siracusa@gmail.com) — absolute icon, we stan. 👑

---

📜 LICENSE 📜

Copyright (c) 2010 by John C. Siracusa. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

---

okay and that's the whole page bestie 🎀 this doc lives in perl v5.34.0, dated 2022-06-17 — that's the Rose::URI(3pm) manual page, and now you know it, so go manipulate some URIs. slay, hydrate, and remember: use URI for the gopher nonsense. 💖✨🦋