curl_escape(3) [php man page]

CURL_ESCAPE(3)								 1							    CURL_ESCAPE(3)

curl_escape - URL encodes the given string

SYNOPSIS

       string curl_escape (resource  $ch, string  $str)

DESCRIPTION

	This function URL encodes the given string according to RFC 3986.

PARAMETERS

	      o $ch
		-A cURL handle returned by curl_init(3).

	      o $str
		- The string to be encoded.

RETURN VALUES

	Returns escaped string or FALSE on failure.

EXAMPLES

       Example #1

	      curl_escape(3) example

	      <?php
	      // Create a curl handle
	      $ch = curl_init();

	      // Escape a string used as a GET parameter
	      $location = curl_escape($ch, 'Hofbrauhaus / Munchen');
	      // Result: Hofbr%C3%A4uhaus%20%2F%20M%C3%BCnchen

	      // Compose an URL with the escaped string
	      $url = "http://example.com/add_location.php?location={$location}";
	      // Result: http://example.com/add_location.php?location=Hofbr%C3%A4uhaus%20%2F%20M%C3%BCnchen

	      // Send HTTP request and close the handle
	      curl_setopt($ch, CURLOPT_URL, $url);
	      curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
	      curl_exec($ch);
	      curl_close($ch);
	      ?>

SEE ALSO

       curl_unescape(3), urlencode(3), rawurlencode(3), RFC 3986.

PHP Documentation Group 													    CURL_ESCAPE(3)

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)