urlencode(1) [debian man page]

URLENCODE(1)							  GridSite Manual						      URLENCODE(1)

NAME

       urlencode - convert strings to or from URL-encoded form

SYNOPSIS

       urlencode [-m|-d] string [string ...]

DESCRIPTION

       urlencode encodes strings according to RFC 1738.

       That is, characters A-Z a-z 0-9 . _ and - are passed through unmodified, but all other characters are represented as %HH, where HH is their
       two-digit    upper-case	  hexadecimal	 ASCII	  representation.     For    example,	 the	URL    http://www.gridpp.ac.uk/    becomes
       http%3A%2F%2Fwww.gridpp.ac.uk%2F

       urlencode  converts  each character in all the strings given on the command line. If multiple strings are given, they are concatenated with
       separating spaces before conversion.

OPTIONS

       -m     Instead of full conversion, do GridSite "mild URL encoding" in which A-Z a-z 0-9 . = - _ @ and / are passed through unmodified. This
	      results  in  slightly more human-readable strings but the application must be prepared to create or simulate the directories implied
	      by any slashes.

       -d     Do URL-decoding rather than encoding, according to RFC 1738. %HH and %hh strings are  converted  and  other  characters  are  passed
	      through unmodified, with the exception that + is converted to space.

EXIT CODES

       0 is always returned.

AUTHOR

       Andrew McNab <Andrew.McNab@manchester.ac.uk>

       urlencode is part of GridSite: http://www.gridsite.org/

urlencode							   November 2003						      URLENCODE(1)

RAWURLENCODE(3) 							 1							   RAWURLENCODE(3)

rawurlencode - URL-encode according to RFC 3986

SYNOPSIS

       string rawurlencode (string  $str)

DESCRIPTION

	Encodes the given string according to RFC 3986.

PARAMETERS

	      o $str
		- The URL to be encoded.

RETURN VALUES

	Returns a string in which all non-alphanumeric characters except -_.~ have been replaced with a percent ( %) sign followed by two hex dig-
       its. This is the encoding described in RFC 3986 for protecting literal characters from being interpreted as special URL delimiters, and for
       protecting URLs from being mangled by transmission media with character conversions (like some email systems).

       Note

	       Prior to PHP 5.3.0, rawurlencode encoded tildes ( ~) as per RFC 1738.

CHANGELOG

       +--------+---------------------------------------------------+
       |Version |						    |
       |	|						    |
       |	|		     Description		    |
       |	|						    |
       +--------+---------------------------------------------------+
       | 5.3.4	|						    |
       |	|						    |
       |	|  Tilde  characters  are  no  longer  encoded when |
       |	| rawurlencode(3) is used with EBCDIC strings.	    |
       |	|						    |
       | 5.3.0	|						    |
       |	|						    |
       |	|	      Now conforms to RFC 3986. 	    |
       |	|						    |
       +--------+---------------------------------------------------+
EXAMPLES

       Example #1

	      including a password in an FTP URL

	      <?php
	      echo '<a href="ftp://user:', rawurlencode('foo @+%/'),
		   '@ftp.example.com/x.txt">';
	      ?>

	      The above example will output:

	      <a href="ftp://user:foo%20%40%2B%25%2F@ftp.example.com/x.txt">

	Or, if you pass information in a PATH_INFO component of the URL:

       Example #2

	      rawurlencode(3) example 2

	      <?php
	      echo '<a href="http://example.com/department_list_script/',
		  rawurlencode('sales and marketing/Miami'), '">';
	      ?>

	      The above example will output:

	      <a href="http://example.com/department_list_script/sales%20and%20marketing%2FMiami">

SEE ALSO

       rawurldecode(3), urldecode(3), urlencode(3), RFC 3986.

PHP Documentation Group 													   RAWURLENCODE(3)