PHP: Predefined Variables

Last updated: Fri, 11 Apr 2008

Predefined Variables

Since PHP 4.1.0, the preferred method for retrieving external variables is with the superglobals mentioned below. Before this time, people relied on either register_globals or the long predefined PHP arrays ($HTTP_*_VARS). Od PHP 5.0.0, długie tablice zmiennych predefiniowanych mogą być wyłączone dyrektywą konfiguracji register_long_arrays.

Server variables: `$_SERVER`

Informacja: Introduced in 4.1.0. In earlier versions, use $HTTP_SERVER_VARS.

$_SERVER is an array containing information such as headers, paths, and script locations. The entries in this array are created by the web server. There is no guarantee that every web server will provide any of these; servers may omit some, or provide others not listed here. That said, a large number of these variables are accounted for in the » CGI 1.1 specification, so you should be able to expect those.

This is a 'superglobal', or automatic global, variable. This simply means that it is available in all scopes throughout a script. You don't need to do a global $_SERVER; to access it within functions or methods, as you do with $HTTP_SERVER_VARS.

$HTTP_SERVER_VARS contains the same initial information, but is not a superglobal. (Note that $HTTP_SERVER_VARS and $_SERVER are different variables and that PHP handles them as such)

If the register_globals directive is set, then these variables will also be made available in the global scope of the script; i.e., separate from the $_SERVER and $HTTP_SERVER_VARS arrays. For related information, see the security chapter titled Using Register Globals. These individual globals are not superglobals.

You may or may not find any of the following elements in $_SERVER. Note that few, if any, of these will be available (or indeed have any meaning) if running PHP on the command line.

'PHP_SELF'

The filename of the currently executing script, relative to the document root. For instance, $_SERVER['PHP_SELF'] in a script at the address http://example.com/test.php/foo.bar would be /test.php/foo.bar. The __FILE__ constant contains the full path and filename of the current (i.e. included) file. If PHP is running as a command-line processor this variable contains the script name since PHP 4.3.0. Previously it was not available.

'argv'

Array of arguments passed to the script. When the script is run on the command line, this gives C-style access to the command line parameters. When called via the GET method, this will contain the query string.

'argc'

Contains the number of command line parameters passed to the script (if run on the command line).

'GATEWAY_INTERFACE'

What revision of the CGI specification the server is using; i.e. 'CGI/1.1'.

'SERVER_ADDR'

The IP address of the server under which the current script is executing.

'SERVER_NAME'

The name of the server host under which the current script is executing. If the script is running on a virtual host, this will be the value defined for that virtual host.

'SERVER_SOFTWARE'

Server identification string, given in the headers when responding to requests.

'SERVER_PROTOCOL'

Name and revision of the information protocol via which the page was requested; i.e. 'HTTP/1.0';

'REQUEST_METHOD'

Which request method was used to access the page; i.e. 'GET', 'HEAD', 'POST', 'PUT'.

Informacja: PHP script is terminated after sending headers (it means after producing any output without output buffering) if the request method was HEAD.

'REQUEST_TIME'

The timestamp of the start of the request. Available since PHP 5.1.0.

'QUERY_STRING'

The query string, if any, via which the page was accessed.

'DOCUMENT_ROOT'

The document root directory under which the current script is executing, as defined in the server's configuration file.

'HTTP_ACCEPT'

Contents of the Accept: header from the current request, if there is one.

'HTTP_ACCEPT_CHARSET'

Contents of the Accept-Charset: header from the current request, if there is one. Example: 'iso-8859-1,*,utf-8'.

'HTTP_ACCEPT_ENCODING'

Contents of the Accept-Encoding: header from the current request, if there is one. Example: 'gzip'.

'HTTP_ACCEPT_LANGUAGE'

Contents of the Accept-Language: header from the current request, if there is one. Example: 'en'.

'HTTP_CONNECTION'

Contents of the Connection: header from the current request, if there is one. Example: 'Keep-Alive'.

'HTTP_HOST'

Contents of the Host: header from the current request, if there is one.

'HTTP_REFERER'

The address of the page (if any) which referred the user agent to the current page. This is set by the user agent. Not all user agents will set this, and some provide the ability to modify HTTP_REFERER as a feature. In short, it cannot really be trusted.

'HTTP_USER_AGENT'

Contents of the User-Agent: header from the current request, if there is one. This is a string denoting the user agent being which is accessing the page. A typical example is: Mozilla/4.5 [en] (X11; U; Linux 2.2.9 i586). Among other things, you can use this value with get_browser() to tailor your page's output to the capabilities of the user agent.

'HTTPS'

Set to a non-empty value if the script was queried through the HTTPS protocol. Note that when using ISAPI with IIS, the value will be off if the request was not made through the HTTPS protocol.

'REMOTE_ADDR'

The IP address from which the user is viewing the current page.

'REMOTE_HOST'

The Host name from which the user is viewing the current page. The reverse dns lookup is based off the REMOTE_ADDR of the user.

Informacja: Your web server must be configured to create this variable. For example in Apache you'll need HostnameLookups On inside httpd.conf for it to exist. See also gethostbyaddr().

'REMOTE_PORT'

The port being used on the user's machine to communicate with the web server.

'SCRIPT_FILENAME'

The absolute pathname of the currently executing script.

Informacja: If a script is executed with the CLI, as a relative path, such as file.php or ../file.php, $_SERVER['SCRIPT_FILENAME'] will contain the relative path specified by the user.

'SERVER_ADMIN'

The value given to the SERVER_ADMIN (for Apache) directive in the web server configuration file. If the script is running on a virtual host, this will be the value defined for that virtual host.

'SERVER_PORT'

The port on the server machine being used by the web server for communication. For default setups, this will be '80'; using SSL, for instance, will change this to whatever your defined secure HTTP port is.

'SERVER_SIGNATURE'

String containing the server version and virtual host name which are added to server-generated pages, if enabled.

'PATH_TRANSLATED'

Filesystem- (not document root-) based path to the current script, after the server has done any virtual-to-real mapping.

Informacja: As of PHP 4.3.2, PATH_TRANSLATED is no longer set implicitly under the Apache 2 SAPI in contrast to the situation in Apache 1, where it's set to the same value as the SCRIPT_FILENAME server variable when it's not populated by Apache. This change was made to comply with the CGI specification that PATH_TRANSLATED should only exist if PATH_INFO is defined. Apache 2 users may use AcceptPathInfo = On inside httpd.conf to define PATH_INFO.

'SCRIPT_NAME'

Contains the current script's path. This is useful for pages which need to point to themselves. The __FILE__ constant contains the full path and filename of the current (i.e. included) file.

'REQUEST_URI'

The URI which was given in order to access this page; for instance, '/index.html'.

'PHP_AUTH_DIGEST'

When running under Apache as module doing Digest HTTP authentication this variable is set to the 'Authorization' header sent by the client (which you should then use to make the appropriate validation).

'PHP_AUTH_USER'

When running under Apache or IIS (ISAPI on PHP 5) as module doing HTTP authentication this variable is set to the username provided by the user.

'PHP_AUTH_PW'

When running under Apache or IIS (ISAPI on PHP 5) as module doing HTTP authentication this variable is set to the password provided by the user.

'AUTH_TYPE'

When running under Apache as module doing HTTP authenticated this variable is set to the authentication type.

Environment variables: `$_ENV`

Informacja: Introduced in 4.1.0. In earlier versions, use $HTTP_ENV_VARS.

These variables are imported into PHP's global namespace from the environment under which the PHP parser is running. Many are provided by the shell under which PHP is running and different systems are likely running different kinds of shells, a definitive list is impossible. Please see your shell's documentation for a list of defined environment variables.

Other environment variables include the CGI variables, placed there regardless of whether PHP is running as a server module or CGI processor.

This is a 'superglobal', or automatic global, variable. This simply means that it is available in all scopes throughout a script. You don't need to do a global $_ENV; to access it within functions or methods, as you do with $HTTP_ENV_VARS.

$HTTP_ENV_VARS contains the same initial information, but is not a superglobal. (Note that $HTTP_ENV_VARS and $_ENV are different variables and that PHP handles them as such)

If the register_globals directive is set, then these variables will also be made available in the global scope of the script; i.e., separate from the $_ENV and $HTTP_ENV_VARS arrays. For related information, see the security chapter titled Using Register Globals. These individual globals are not superglobals.

HTTP Cookies: `$_COOKIE`

Informacja: Introduced in 4.1.0. In earlier versions, use $HTTP_COOKIE_VARS.

An associative array of variables passed to the current script via HTTP cookies. Automatically global in any scope.

This is a 'superglobal', or automatic global, variable. This simply means that it is available in all scopes throughout a script. You don't need to do a global $_COOKIE; to access it within functions or methods, as you do with $HTTP_COOKIE_VARS.

$HTTP_COOKIE_VARS contains the same initial information, but is not a superglobal. (Note that $HTTP_COOKIE_VARS and $_COOKIE are different variables and that PHP handles them as such)

If the register_globals directive is set, then these variables will also be made available in the global scope of the script; i.e., separate from the $_COOKIE and $HTTP_COOKIE_VARS arrays. For related information, see the security chapter titled Using Register Globals. These individual globals are not superglobals.

HTTP GET variables: `$_GET`

Informacja: Introduced in 4.1.0. In earlier versions, use $HTTP_GET_VARS.

An associative array of variables passed to the current script via the HTTP GET method. Automatically global in any scope.

This is a 'superglobal', or automatic global, variable. This simply means that it is available in all scopes throughout a script. You don't need to do a global $_GET; to access it within functions or methods, as you do with $HTTP_GET_VARS.

$HTTP_GET_VARS contains the same initial information, but is not a superglobal. (Note that $HTTP_GET_VARS and $_GET are different variables and that PHP handles them as such)

If the register_globals directive is set, then these variables will also be made available in the global scope of the script; i.e., separate from the $_GET and $HTTP_GET_VARS arrays. For related information, see the security chapter titled Using Register Globals. These individual globals are not superglobals.

HTTP POST variables: `$_POST`

Informacja: Introduced in 4.1.0. In earlier versions, use $HTTP_POST_VARS.

An associative array of variables passed to the current script via the HTTP POST method. Automatically global in any scope.

This is a 'superglobal', or automatic global, variable. This simply means that it is available in all scopes throughout a script. You don't need to do a global $_POST; to access it within functions or methods, as you do with $HTTP_POST_VARS.

$HTTP_POST_VARS contains the same initial information, but is not a superglobal. (Note that $HTTP_POST_VARS and $_POST are different variables and that PHP handles them as such)

If the register_globals directive is set, then these variables will also be made available in the global scope of the script; i.e., separate from the $_POST and $HTTP_POST_VARS arrays. For related information, see the security chapter titled Using Register Globals. These individual globals are not superglobals.

HTTP File upload variables: `$_FILES`

Informacja: Introduced in 4.1.0. In earlier versions, use $HTTP_POST_FILES.

An associative array of items uploaded to the current script via the HTTP POST method. Automatically global in any scope.

This is a 'superglobal', or automatic global, variable. This simply means that it is available in all scopes throughout a script. You don't need to do a global $_FILES; to access it within functions or methods, as you do with $HTTP_POST_FILES.

$HTTP_POST_FILES contains the same information, but is not a superglobal. (Note that $HTTP_POST_FILES and $_FILES are different variables and that PHP handles them as such)

If the register_globals directive is set, then these variables will also be made available in the global scope of the script; i.e., separate from the $_FILES and $HTTP_POST_FILES arrays. For related information, see the security chapter titled Using Register Globals. These individual globals are not superglobals.

Request variables: `$_REQUEST`

Informacja: Introduced in 4.1.0. There is no equivalent array in earlier versions.

Informacja: Prior to PHP 4.3.0, $_FILES information was also included in $_REQUEST.

An associative array consisting of the contents of $_GET, $_POST, and $_COOKIE.

This is a 'superglobal', or automatic global, variable. This simply means that it is available in all scopes throughout a script. You don't need to do a global $_REQUEST; to access it within functions or methods.

If the register_globals directive is set, then these variables will also be made available in the global scope of the script; i.e., separate from the $_REQUEST array. For related information, see the security chapter titled Using Register Globals. These individual globals are not superglobals.

Session variables: `$_SESSION`

Informacja: Introduced in 4.1.0. In earlier versions, use $HTTP_SESSION_VARS.

An associative array containing session variables available to the current script. See the Session functions documentation for more information on how this is used.

This is a 'superglobal', or automatic global, variable. This simply means that it is available in all scopes throughout a script. You don't need to do a global $_SESSION; to access it within functions or methods, as you do with $HTTP_SESSION_VARS.

$HTTP_SESSION_VARS contains the same information, but is not a superglobal. (Note that $HTTP_SESSION_VARS and $_SESSION are different variables and that PHP handles them as such)

If the register_globals directive is set, then these variables will also be made available in the global scope of the script; i.e., separate from the $_SESSION and $HTTP_SESSION_VARS arrays. For related information, see the security chapter titled Using Register Globals. These individual globals are not superglobals.

Global variables: `$GLOBALS`

An associative array containing references to all variables which are currently defined in the global scope of the script. The variable names are the keys of the array.

This is a 'superglobal', or automatic global, variable. This simply means that it is available in all scopes throughout a script. You don't need to do a global $GLOBALS; to access it within functions or methods.

The previous error message: `$php_errormsg`

$php_errormsg is a variable containing the text of the last error message generated by PHP. This variable will only be available within the scope in which the error occurred, and only if the track_errors configuration option is turned on (it defaults to off).

Raw POST data: `$HTTP_RAW_POST_DATA`

$HTTP_RAW_POST_DATA contains the raw POST data. See always_populate_raw_post_data

HTTP response headers: `$http_response_header`

The $http_response_header array is similiar to the get_headers() function. When using the HTTP wrapper $http_response_header will be populated with the HTTP response headers.

Predefined Classes

List of Reserved Words

Last updated: Fri, 11 Apr 2008

add a note User Contributed Notes
Predefined Variables

moochm@gmail
07-Apr-2008 06:15


When using a php script like a remote function call, I find something like this useful for setting default parameters.



<?php

/**

/* combine _GET _POST _COOKIE variables with provided default values

/* defaults - associative array of default values

/* overwrite - if true, write result to _REQUEST superglobal

/* super_globals - array of super globals to fetch values from

**/

function get_params($defaults = null, $overwrite = false, $super_globals = array('_GET', '_POST', '_COOKIE'))

{

    $ret = array();



    // fetch values from request

    foreach($super_globals as $sg)

        foreach($GLOBALS[$sg] as $k=>$v)

            $ret[$k] = $v;



    // apply defaults for missing parameters

    if($defaults) foreach($defaults as $k=>$v)

        if(!isset($ret[$k]))

            $ret[$k] = $v;



    if($overwrite)

        $_REQUEST = $ret;



    return $ret;

}



// Example: page.php?style=modern



$argv = get_params(array('id'=>42, 'style'=>'medieval'));



// $argv['id'] = 42

// $argv['style'] = 'modern'



?>

Typer85 at gmail dot com
19-Feb-2008 12:56


Note the manual entry for PHP_SELF states the following:



"The filename of the currently executing script, relative to the document root. For instance, $_SERVER['PHP_SELF'] in a script at the address http://example.com/test.php/foo.bar  would be /test.php/foo.bar."



However I did some vigorous testing on three different machines and this note is not always true. The results are given below:



Given a URL of http://www.example.com/Info.php/Page/Home



Apache 2.2.4/Win32/PHP 5.2.2/Apache 2.0 Handler

----> PHP_SELF = Info.php/Page/Home



Apache 1.3.37/Unix/PHP 5.2.2/CGI

----> PHP_SELF = Info.php



Apache 1.3.33/Unix/5.1.4/FastCGI

----> PHP_SELF = Info.php



To be completely honest, I am not sure why this is the case; perhaps there is a setting in Apache to modify this option, but in either case take careful consideration of this note.

spamtrap at scottydm dot com
13-Feb-2008 03:15


I was a little frustrated by the fact that some of the _SERVER variables didn't seem to exist, so I did a bit of Googling and found the answer: many of these variables are supplied by the web server and not all web servers supply the same set of variables.



I found a comparison between Apache v1.3.29 and IIS v5.1 on this page: http://koivi.com/apache-iis-php-server-array.php Useful for those of us doing cross-platform development.



While running experiments with different browsers I noticed some of the HTTP_* variables come and go depending on the browser used, or in the case of Opera by diddling the "user mode" (the widget that lets you look at a page as text only, etc.). For example: in IE and Opera HTTP_KEEP_ALIVE was missing, but was present in Firefox and Mozilla, and when I fiddled with Opera's "user mode" I got somethings called HTTP_TE and HTTP_CACHE_CONTROL.



So, what you get is dependent on the web server AND the browser.



I did see one IIS supplied variable not on that list: REQUEST_TIME, which seems to be in Unix timestamp format.



While researching this I discovered there are plenty of people who have their phpinfo() page visible and indexed on a few search engines. For those who want to dig a bit deeper than that nice web page comparing Apache to IIS, looking at other peoples' phpinfo() pages could be useful. You get the version of PHP plus OS and web server they use, along with all the _SERVER variables. I found the highest percent of signal-to-noise by searching for "phpinfo()" (with the quotes) on Dogpile: http://www.dogpile.com/

php-net dot ucn dot extranet dot sys at dark-chiaki dot net
13-Dec-2007 05:40


In addition to mfyahya at gmail dot com (2007-06-07 03:33):



If You are working with the Apache module mod_rewrite and want to set some environment vars, the Apache manual says this vars could be accessed in CGI using $ENV{VAR}. In PHP You might want to write $_ENV['VAR'] to get the value of VAR, but You have to access if via $_SERVER, and in some different ways:



1. Example: .htaccess and example.php



RewriteEngine on

RewriteRule ^?var1=([^;]*);var2=([^;]*)$ \

 - [E=VAR1:$1,E=VAR2:$2]



<?php echo($_SERVER['VAR1']."\r\n"

          .$_SERVER['VAR2']); ?>



2. Example: .htaccess and index.php



RewriteEngine on

RewriteRule ^index\.php$ - [L]

RewriteRule ?var1=([^;]*);var2=([^;]*)$ \

 index.php [E=VAR1:$1,E=VAR2:$2]



<?php echo($_SERVER['REDIRECT_VAR1']."\r\n"

          .$_SERVER['REDIRECT_VAR2']); ?>



Note: If any RewriteRule matches, an internal redirect than restarts (after the last defined rule, or immediately after the matched rule having a L-flag) checking the entire rule set again. For an internal redirect every defined VAR gets an 'REDIRECT_' prefix, i.e. VAR1 will be REDIRECT_VAR1, VAR2 will be REDIRECT_VAR2.



Of course, You can (additionally) redefine the original VAR:



RewriteEngine on

RewriteRule ^index\.php$ \

 - [E=VAR1:%{REDIRECT_VAR1},E=VAR2:%{REDIRECT_VAR2},L]

RewriteRule ?var1=([^;]*);var2=([^;]*)$ \

 index.php [E=VAR1:$1,E=VAR2:$2]



With this, You will have $_SERVER['REDIRECT_VAR*'] -and- $_SERVER['VAR*'].



***



The given examples are only for explanation, in any case they are not intended to fit Your needs. The "\<CRLF><SP>" in the .htaccess examples are only for display purpose, they should not occur in a real .htaccess file. The argument separator ';' in links can also be '&', but this may cause some trouble with HTML/XHTML. See the following pages for more information about this issue:

- http://www.w3.org/TR/html4/appendix/notes.html#h-B.2.2

- http://www.w3.org/QA/2005/04/php-session

Nicolae Namolovan
22-Nov-2007 08:49


SECURITY RISK !



Never ever trust the values that comes from $_SERVER.



HTTP_X_FORWARDED, HTTP_X_FORWARDED_FOR, HTTP_FORWARDED_FOR, HTTP_FORWARDED, etc.. can be spoofed !



To get the ip of user, use only $_SERVER['REMOTE_ADDR'], otherwise the 'ip' of user can be easily changed by sending a HTTP_X_* header, so user can escape a ban or spoof a trusted ip.



Of course this is well know, but I don't see it mentioned in these notes..



If you use the ip only for tracking (not for any security features like banning or allow access to something by ip), you can also use HTTP_X_FORWARDED to get user's ip what are behind proxy.

crescentfreshpot at yahoo dot com
14-Nov-2007 07:03


In response to mathiasrav's getip() implementation on 28-Jul-2007, it should be noted that it:



- assumes IPv4 addresses only

- returns $_SERVER['REMOTE_ADDR'] for any value of $_SERVER['HTTP_CLIENT_IP'] that matches 127.0.*.*, 192.168.*.* or 10.0.*.*, which is not desirable if you actually WANT the value of HTTP_CLIENT_IP



dlyaza's prior snippet has neither of these problems.

root at mantoru dot de
01-Nov-2007 03:59


Note that some headers will be checked for validity (by Apache, I suppose) before showing up in $_SERVER -- If-Modified-Since for example.



<?php

$lastmod = gmdate('D, d M Y H:i:s', filemtime('somefile'));

header("Last-Modified: $lastmod");

?>



This WON'T work, "GMT" is missing. Internet Explorer auto-fixes this by adding GMT, while Firefox resends this data as-is. (So an If-Modified-Since-header is sent, but neither shows up in $_SERVER nor in apache_request_headers()). This would be correct:



<?php

$lastmod = gmdate('D, d M Y H:i:s', filemtime('somefile')) . 'GMT';

header("Last-Modified: $lastmod");

?>

jsan
19-Oct-2007 09:39


@White-Gandalf: one can control this behavior by setting:



UseCanonicalName On|Off



in their apache config (at least, on *ix platforms).



On => $_SERVER['SERVER_NAME'] is the ServerName var from either the global server or virtual host, whichever wraps the PHP app closest.



Off => Whatever was in the Host: header sent by the client.

White-Gandalf
16-Oct-2007 04:01


'SERVER_NAME' does NOT necessarily refer to the name of a virtual host or any other things defined in the apache config.

Instead it simply takes the value of the "Host:" entry of the HTTP-header sent by the client.

At least with apache version 2.2.5 on Windows.

phpnotes dot 20 dot zsh at spamgourmet dot com
21-Sep-2007 05:45


The headers sent by the browser will be stored in the $_SERVER array -- they will get capitalized and prefixed with HTTP. So a header like "X-Foo-Bar: Baz" will result in <?php $_SERVER['HTTP_X_FOO_BAR'] = 'Baz';?>. This is why you should use isset before using e.g. HTTP_ACCEPT_LANGUAGE, 'cause it may not be set.



The only exception I know from that is HTTP_X_ORIGINAL_URI, which is always set and holds the current URL without querystring. But you can't trust that too because it can be overriden by sending a X-Original-URI header.

andres at andresj dot ath dot cx
05-Aug-2007 06:41


To get the directory of the current script: (I think this is a little more resource-friendly, but then again with all the fast computers available, it does not matter so much...)

<?

// For the script that is running:

$script_directory = substr($_SERVER['SCRIPT_FILENAME'], 0, strrpos($_SERVER['SCRIPT_FILENAME'], '/'));

// If your script is included from another script:

$included_directory = substr(__FILE__, 0, strrpos(__FILE__, '/'));

echo $script_directory . '<br />';

echo $included_directory . '<br />';

?>

If you have a script that only includes the script written above in a directory called 'includer', and I access it from a web browser, this will be what I see:



/path/to/includer/

/path/to/included/

deceze at gmail dot YesThatsGoogleMail dot com
11-Apr-2007 04:37


If you're working with $_GET a lot and need to preserve already set variables in a link for the next page, this function is pretty handy for simplifying the process of generating a new URL:



string setUrlVariables([string var, string value], [varN, valueN], ...)



<?php



function setUrlVariables() {

  $arg = array();

  $string = "?";

  $vars = $_GET;

  for ($i = 0; $i < func_num_args(); $i++)

    $arg[func_get_arg($i)] = func_get_arg(++$i);

  foreach (array_keys($arg) as $key)

    $vars[$key] = $arg[$key];

  foreach (array_keys($vars) as $key)

    if ($vars[$key] != "") $string.= $key . "=" . $vars[$key] . "&";

  if (SID != "" && SID != "SID" && $_GET["PHPSESSID"] == "")

    $string.= htmlspecialchars(SID) . "&";



  return htmlspecialchars(substr($string, 0, -1));

}



?>



You use it like this:



<a href="nextpage.php<?php echo setUrlVariables(); ?>">Link</a>



In this case setUrlVariables() will simply add all the $_GET variables of the current page/URL and even takes care of the PHPSESSID if you use one (and didn't change the default variable name). The above HREF would complete to e.g.:



"nextpage.php?var=21&amp;PHPSESSID=BI89J"



If you supply arguments, do it like this:



<?php echo setUrlVariables("user", "foobar"); ?>



This would complete the HREF to e.g.:



"nextpage.php?user=foobar&amp;var=21&amp;PHPSESSID=BI89J"



Unsetting variables works by supplying an empty value:



<?php echo setUrlVariables("var", ""); ?>



"nextpage.php?user=foobar&amp;PHPSESSID=BI89J"



setUrlVariables() also makes sure it produces "pretty URLs", so it doesn't output any unnecessary garbage. ;)



<?php

  session_destroy();

  echo setUrlVariables("user", "");

?>



"nextpage.php"

danvasile at pentest dot ro
21-Mar-2007 09:22


If you have problems with $_SERVER['HTTPS'], especially if it returns no values at all you should check the results of phpinfo(). It might not be listed at all. 

Here is a solution to check and change, if necessary, to ssl/https that will work in all cases:



<?php

if ($_SERVER['SERVER_PORT']!=443) {

$sslport=443; //whatever your ssl port is

$url = "https://". $_SERVER['SERVER_NAME'] . ":" . $sslport . $_SERVER['REQUEST_URI'];

header("Location: $url");

}

?>



Of course, this should be done before any html tag or php echo/print.

Joe Marty
24-Jan-2007 08:53


I think it is very important to note that PHP will automatically replace dots ('.') AND spaces (' ') with underscores ('_') in any incoming POST or GET (or REQUEST) variables.



This page notes the dot replacement, but not the space replacement:

http://us2.php.net/manual/en/language.variables.external.php



The reason is that '.' and ' ' are not valid characters to use in a variable name.  This is confusing to many people, because most people use the format $_POST['name'] to access these values.  In this case, the name is not used as a variable name but as an array index, in which those characters are valid.



However, if the register_globals directive is set, these names must be used as variable names.  As of now, PHP converts the names for these variables before inserting them into the external variable arrays, unfortunately - rather than leaving them as they are for the arrays and changing the names only for the variables set by register_globals.



If you want to use:

<input name="title for page3.php" type="text">



The value you will get in your POST array, for isntance would be:

$_POST['title_for_page3_php']

NeoSmart Technologies
18-Nov-2006 03:22


The *only* way to make Request_URI work as a 100% Apache-Compliant server variable on IIS/Windows is to use an Isapi Filter - as documented at http://neosmart.net/blog/archives/291 . The various steps mentioned below *completely* fail when a rewrite engine is employed, since IIS will *never* return a non-existent path (i.e. the actual pretty-URI used) via its server variables. 



This also applies to accessing index.php via a folder.

For instance, calls made to /folder/ will appear as /folder/index.php and not /folder/.



The fix is to use the ISAPI filter provided at http://neosmart.net/blog/archives/291



You don't have to modify any of the actual scripts once this filter is in place - it automatically intercepts calls to REQUEST_URI and replaces them with the actual user-entered path.

me at tommygeorge dot com
09-Nov-2006 05:59


I'm sure this is elsewhere, but since 'chris dot chaudruc at gmail dot com' posted his example, I thought I would share a quick function I use to force HTTPS protocol on a page, without having to know the scripts name...



<?php

function ForceHTTPS() 

{

    if( $_SERVER['HTTPS'] != "on" )  

    { 

       $new_url = "https://" . $_SERVER['SERVER_NAME'] . $_SERVER['REQUEST_URI']; 

       header("Location: $new_url");

       exit;

    } 

}

?>



Correct me if part of this doesn't work right. I've always used *nix based servers for PHP, so I might not be aware of certain windows limitations. Thanks.

Alexander Hars
19-Sep-2006 11:16


If you want to use a form with multiple checkboxes (e.g. one per row) and assign the same name to each checkbox then the name needs to end with []. This tells PHP to put all checked values into an array variable. 

For example:

<input type="checkbox" name="id[]" value="value_1">

<input type="checkbox" name="id[]" value="value_2">

..

<input type="checkbox" name="id[]" value="value_x">



You can now retrieve all values by using: 

   $values = $_POST['id'];



If the name does not end with [], then only a single value will be available via the $_POST variable even if the user checks several checkboxes.

jameslporter at gmail dot com
05-May-2006 09:19


Refer to CanonicalName if you are not getting the ServerName in the $_SERVER[SERVER_NAME] variable....This was a pain to figure out for me...now it works as expected by turning canonical naming on.



http://www.apacheref.com/ref/http_core/UseCanonicalName.html

tchamp
26-Apr-2006 04:24


Be careful with HTTP_HOST behind a proxy server.   Use these instead.

[HTTP_X_FORWARDED_FOR] 

[HTTP_X_FORWARDED_HOST] 

[HTTP_X_FORWARDED_SERVER]



In my situation, I used [HTTP_X_FORWARDED_SERVER] in place of [HTTP_HOST] in order get the machine and hostname (www.myurl.com)

Ben XO
14-Apr-2006 03:18


So you have an application in your web space, with a URL such as this:



http://<host>/<installation_path>/



and pages such as



http://<host>/<installation_path>/subfolder1/subfolder2/page.php



You have a file called config.php in <installation_path> which is include()d by all pages (in subfolders or not).



How to work out <installation_path> without hard-coding it into a config file? 



<?php



// this is config.php, and it is in <installation_path>

// it is included by <installation_path>/page.php

// it is included by <installation_path>/subfolder/page2.php

// etc



$_REAL_SCRIPT_DIR = realpath(dirname($_SERVER['SCRIPT_FILENAME'])); // filesystem path of this page's directory (page.php)

$_REAL_BASE_DIR = realpath(dirname(__FILE__)); // filesystem path of this file's directory (config.php)

$_MY_PATH_PART = substr( $_REAL_SCRIPT_DIR, strlen($_REAL_BASE_DIR)); // just the subfolder part between <installation_path> and the page



$INSTALLATION_PATH = $_MY_PATH_PART

    ? substr( dirname($_SERVER['SCRIPT_NAME']), 0, -strlen($_MY_PATH_PART) )

    : dirname($_SERVER['SCRIPT_NAME'])

; // we subtract the subfolder part from the end of <installation_path>, leaving us with just <installation_path> :)



?>

todd dot kisov at yahoo dot com
03-Apr-2006 11:11


To convert query string parameter values ($_GET, $_REQUEST), which include escaped Unicode values resulting from applying the JavaScript "escape" function to a Unicode string (%uNNNN%uNNNN%uNNNN) fast and simple is to use PECL JSON extension:



function JavaScript_Unicode_URL_2_Str($js_uni_str) {

        $res = preg_replace('/%u([[:alnum:]]{4})/', '\\u\1', $js_uni_str);

        $res = str_replace('"', '\"', $res); // if in str "

        $res = json_decode('["'.$res.'"]'); // JavaScrip array with string element

        $res = $res[0];

        $res = iconv('UTF-8', ini_get('default_charset'), $res);

        return $res;

    }

01-Apr-2006 07:56


I was unable to convince my hosting company to change their installation of PHP and therefore had to find my own way to computer $_SERVER["DOCUMENT_ROOT"].  I eventually settled on the following, which is a combination of earlier notes (with some typos corrected):



<?php

if ( ! isset($_SERVER['DOCUMENT_ROOT'] ) )

  $_SERVER['DOCUMENT_ROOT'] = str_replace( '\\', '/', substr(

    $_SERVER['SCRIPT_FILENAME'], 0, 0-strlen($_SERVER['PHP_SELF']) ) );

?>

mjs at beebo dot org
30-Mar-2006 11:24


Note that PHP_SELF will not be equal to REQUEST_URI under Apache if mod_rewrite has been used to move one URL to another--PHP_SELF will contain the rewritten address, and REQUEST_URI will contain the URL the user sees in their browser.

Aardvark
07-Mar-2006 10:35


$_GET may not handle query string parameter values which include escaped Unicode values resulting from applying the JavaScript "escape" function to a Unicode string.

To handle this the query parameter value can be obtained  using a function such as:



function getQueryParameter ($strParam) {

  $aParamList = explode('&', $_SERVER['QUERY_STRING']);

  $i = 0;

  while ($i < count($aParamList)) {

    $aParam = split('=', $aParamList[$i]);

    if ($strParam == $aParam[0]) {

      return $aParam[1];

    } 

  }

  return "";

}



or by directly building an array or query string values and then processing the parameter string using a function such as the "unescape" function which can be found at http://www.kanolife.com/escape/2006/03/unicode-url-escapes-in-php.html (or http://www.kanolife.com/escape/ for related info).

justin dot (nospam)george at gmail dot com
28-Feb-2006 09:00


Note that it's a very, very bad idea to append to global variables in a loop, unless you really, really mean to do so in a global context. I just a while ago hung my server with a snippet of code like this:



<?php

$host  = $_SERVER['HTTP_HOST'];

$uri  = rtrim($_SERVER['PHP_SELF'], "/\\");



   

$GLOBALS['SITE_ROOT'] = "http://$host$uri";



while ($i < somenumber)

readfile($GLOBALS['SITE_ROOT'] = $GLOBALS['SITE_ROOT'] . '/this/file.php');

$i++

}

?>



While it is an entertaining and unusual method of creating very long URLs and breaking servers, it's a pretty awesomely bad idea 



(Especially considering that the script in question ran concurrently with others of it's type, so the value in $GLOBALS['SITE_ROOT'] was unknown.)

nathan
22-Feb-2006 05:05


Also on using IPs to look up country & city, note that what you get might not be entirely accurate.  If their ISP is based in a different city or province/state, the IPs may be owned by the head office, and used across several areas.  

You also have rarer situations where they might be SSHed into another server, on the road, at work, at a friend's...  It's a nice idea, but as the example code shows, it should only be used to set defaults.

marsh at NOSPAM-TAKETHATSPAMMER dot uri
20-Jan-2006 05:05


The solution advanced by info at meshkaat dot com does not work correctly on machines with IIS configured to use

a virtual directory as the launch point. The address strings for $_SERVER['SCRIPT_FILENAME'] and $_SERVER['PHP_SELF'] will not necessarily have the same name for the highest level directory in $_SERVER['PHP_SELF'], and therefore this solution will not return the proper value.

marsh at NOSPAM-TAKETHATSPAMMER dot uri dot edu
12-Jan-2006 04:57


Under Windows XP SP2 and IIS, $_SERVER('x') returns a path using forward slash '/' as the separator, where x is:



      PHP_SELF, SCRIPT_NAME



These arguments, however, all return a path using backward slash, '\' as the separator:



  __FILE__, SCRIPT_FILENAME, and DOCUMENT_ROOT (if you use one of the methods mentioned previously).



Also note that if the name of the last directory in the document root includes a space, the methods described above for setting DOCUMENT_ROOT will return a value that drops the everything past the space.

chris at vault5 dot com
30-Nov-2005 04:17


Since $_SERVER['DOCUMENT_ROOT'] is not always present, the following will provide it where $_SERVER dosen't.



<?php

function resolveDocumentRoot() {

    $current_script = dirname($_SERVER['SCRIPT_NAME']);

    $current_path   = dirname($_SERVER['SCRIPT_FILENAME']);

    

    /* work out how many folders we are away from document_root

       by working out how many folders deep we are from the url.

       this isn't fool proof */

    $adjust = explode("/", $current_script);

    $adjust = count($adjust)-1;

    

    /* move up the path with ../ */

    $traverse = str_repeat("../", $adjust);

    $adjusted_path = sprintf("%s/%s", $current_path, $traverse);



    /* real path expands the ../'s to the correct folder names */

    return realpath($adjusted_path);    

}



?>



It counts the number of folders down the path we are in the URL, then moves that number of folders up the current path... end result should be the document root :)



It wont work with virtual folders or in any situation where the folder in the URL dosen't map to a real folder on the disk (like when using rewrites).

webmaster at eclipse dot org
11-Oct-2005 05:01


In response to tobias at net-clipping dot de



It is not an Apache bug.  Please read http://httpd.apache.org/docs/2.1/mod/core.html#errordocument carefully (2.1 version here, 2.0 and 1.x is similar).  



In short, if your ErrorDocument start with http:// Apache sends a redirect (302) to the error document, hence losing your original referer. If your ErrorDocument points to a relative path, 404 is maintained and so are your variables.



From the Apache manual:



"Note that when you specify an ErrorDocument  that points to a remote URL (ie. anything with a method such as http in front of it), Apache will send a redirect to the client to tell it where to find the document, even if the document ends up being on the same server. This has several implications, the most important being that the client will not receive the original error status code, but instead will receive a redirect status code. This in turn can confuse web robots and other clients which try to determine if a URL is valid using the status code. In addition, if you use a remote URL in an ErrorDocument 401, the client will not know to prompt the user for a password since it will not receive the 401 status code. Therefore, if you use an ErrorDocument 401 directive then it must refer to a local document."



D.

drew dot griffiths at clare dot net
30-Sep-2005 05:51


Re: You can take advantage of 404 error to an usable redirection using REQUEST_URI ...



Whilst this is effective, a line in the .htaccess such as:



RewriteEngine On

RewriteRule ^profiles/([A-Za-z0-9-]+) showprofile.php?profile=$1 [L,NC,QSA]



will throw the requested profile in a variable $profile to the showprofile.php page.  



You can further enhance the url (e.g http://servername/profiles/Jerry/homeaddress/index.htm) and the second variable value homeaddress becomes available in $url_array[3] when used below $url_array=explode("/",$_SERVER['REQUEST_URI']);   



Hope this helps - Works well for me



Drew

Angelina Bell
04-Aug-2005 05:55


Warning:

$_SERVER['PHP_SELF'] and $_SERVER['SCRIPT_NAME'] may not always be set correctly.

Some web hosts implement php as a CGI in such a way that they can turn it on or off for each virtual domain.  Several $_SERVER and $_ENV variable values may be incorrect for documents in subdirectory subdomains of these virtual domains.



An include-file function or constant, instead of PHP_SELF or some other predefined variable throughout a website, will make it easier to "fix" an entire website in case something changes.

<?php

function true_url_path() {

// Pick the predefined variable that works on your server

      return $_ENV['SCRIPT_URL'];

}

?>

Or

<?php

// Pick the predefined variable that works on your server

define("TRUE_URL_PATH", $_ENV['SCRIPT_URL']);

?>

Gregory Boshoff
31-Jul-2005 11:41


$_SERVER['QUERY_STRING'] 



Does not contain XHTML 1.1 compliant ampersands i.e. &amp;



So you will need to do something like this if you are to use $_SERVER['QUERY_STRING'] in URL's.



//  XHTML 1.1 compliant ampersands 

$_SERVER['QUERY_STRING'] = 

str_replace(array('&amp;', '&'), array('&', '&amp;'), 

$_SERVER['QUERY_STRING']);

New York PHP
24-Jul-2005 03:59


Warning: $_SERVER['PHP_SELF'] can include arbitrary user input. The documentation should be updated to reflect this.



The request "http://example.com/info.php/attack%20here" will run /info.php, but in Apache $_SERVER['PHP_SELF'] will equal "/info.php/attack here". This is a feature, but it means that PHP_SELF must be treated as user input.



The attack string could contain urlencoded HTML and JavaScript (cross-site scripting) or it could contain urlencoded linebreaks (HTTP response-splitting).



The use of $_SERVER['SCRIPT_NAME'] is recommended instead.

daniel at softel dot jp
16-Jul-2005 08:43


Note that $php_errormsg may contain a newline character. This can be problematic if you are trying to output it with a JavaScript "alert()" for example.

andy dot gajetzki at gmail dot com
06-Jul-2005 03:22


I wanted to be able to embed a variable in the path. This is useful when, for example, images are rendered on the fly and you would like them to have different urls. 



Here is an illustration:



www.somesite.com/image.php/IMAGETEXTHERE



This would return an image with the text after "image.php/" contained in it. 



I could not recall the name of this feature, so I made a work-around in PHP...



<?        

        

function getPathVariables() {

        $sPathPS = $_SERVER[PHP_SELF];

        $sPathFS = __FILE__;



        $aPathPS = array_reverse(explode("/", $sPathPS));

        $aPathFS = array_reverse(explode("/", $sPathFS));



        $aImageArgs = array();

        $x = 0;



        while ( $aPathPS[$x] != $aPathFS[$x] && $aPathPS[$x] != $aPathFS[0] ) {

                array_unshift($aImageArgs, $aPathPS[$x])        ;

                $x++;

        }

        return $aImageArgs;



}

?>



This function will return an array containing each "/" delimited portion of the path after the script name itself.

notes at arbee dot co dot uk
27-Jun-2005 04:14


Note that $_SERVER['QUERY_STRING'] behaves differently under IIS/Apache.



In Apache (at least on Windows) it is ALWAYS set - if no query string was specified in the URL, $_SERVER['QUERY_STRING'] is initialised as an empty string.



In IIS, if no query string is included in the URL, $_SERVER['QUERY_STRING'] is NOT SET, so trying to access it without checking for its existence will generate notices.

xangelusx at hotmail dot com
13-Jun-2005 10:03


A note about the QUERY_STRING variable when using IIS:



I have found that IIS does not handle large query strings gracefully when passed from PHP. In addition to truncating them to around 1024 kb, I have seen IIS actually add data from other server variables to the end of the truncated data. 



This occurred on Windows 2000 server running IIS 5.0 and PHP 4.3.8.  The problem did not occur when handled by Apache, even on another Windows server.



Note: I realize passing this much data is best accomplished using the POST method, which would avoid this problem all together. I'm merely detailing a problem that I came across.



I have created a page that includes the (very long) query string that was used and some of the results that I saw while testing. It can be viewed at http://www.csb7.com/test/php_iis_qs_limit/. I didn't want to include it here as it would stretch the page out significantly.



~Chris Bloom

mfyahya at gmail dot com
07-Jun-2005 03:33


If you use Apache's redirection features for custom error pages or whatever, the following Apache's REDIRECT variables are also available in $_SERVER:

$_SERVER['REDIRECT_UNIQUE_ID]' 

$_SERVER['REDIRECT_SCRIPT_URL]' 

$_SERVER['REDIRECT_SCRIPT_URI]' 

$_SERVER['REDIRECT_SITE_ROOT]' 

$_SERVER['REDIRECT_SITE_HTMLROOT]' 

$_SERVER['REDIRECT_SITE_CGIROOT]' 

$_SERVER['REDIRECT_STATUS]' 

$_SERVER['REDIRECT_QUERY_STRING]' 

$_SERVER['REDIRECT_URL]' 



I'm not sure if this is a complete list though

exaton at free dot fr
06-May-2005 08:23


With the arrival of the Google Web Accelerator, the problem of keeping track of users through $_SERVER['REMOTE_ADDR'] (for a much shorter while than with cookies) has reared its ugly head anew.



For those confronted with this issue, remember that Google implements the $_SERVER['HTTP_X_FORWARDED_FOR'] header giving the IP address of the connection that it proxies.



Hope this helps...

inbox at tanasity dot com
13-Apr-2005 03:23


Under Windows 2000, running IIS and PHP 4.3.10, $_SERVER['SCRIPT_NAME'] is not available, however $_SERVER['SCRIPT_FILENAME'] is present and seems to contain the same information.

28-Feb-2005 03:41


Matt Johnson says that one should never urldecode() $_GET data. This is incorrect.



If magic_quotes_gpc is turned off in php.ini, then you *do* need to urldecode() $_GET data.



Having magic_quotes_gpc turned off is considered good practise.

Gregory Boshoff
14-Feb-2005 01:19


The Environment variable $ENV is useful for coding portable platform specific application constants. 



// Define a Windows or else Linux root directory path

$_ENV['OS'] == 'Windows_NT' ? $path = 'L:\\www\\' : $path = ' /var/www/';



define('PATH', $path);



echo PATH;

magotes[at]netcabo.pt
12-Feb-2005 04:09


Sorry if this is old news to some, but it might not be obvious at a first glance:



If you are using $_SERVER['remote_addr'] as a way to keep track of a logged-in user (this can be useful to avoid several types of hacking), remember that it might not be the user's actual IP address!



I was trying to implement a login feature that used this, storing the IP into a DB. It went smoothly while on a LAN, but wrecked havoc when accepting outter connections.

niles AT atheos DOT net
26-Jan-2005 09:51


If your having problems returning $_SERVER variables using apache, be sure you enable:



ExtendedStatus On



in your httpd.conf file.



If it's off, then things like $_SERVER['HTTP_HOST'] won't be present.

marcus at lastcraft dot com
24-Jan-2005 01:02


The variable $php_errormsg is not populated if you have XDebug running.

dotpointer
09-Jan-2005 10:26


Running Xitami in Windows 2000 and PHP 4.3.7, nor PHP_SELF or SCRIPT_FILENAME is not availiable. Trying SCRIPT_NAME instead. Here is a function that returns the filename of a script without slashes. Good for use in HTML FORM ACTION=""-arguments...



function getThisFile() {



 /* try to use PHP_SELF first... */

 if (!empty($_SERVER['PHP_SELF'])) {

  $strScript = $_SERVER['PHP_SELF'];

 /* otherwise, try SCRIPT_NAME */

 } else if (!empty($_SERVER['SCRIPT_NAME'])) {

  $strScript = @$_SERVER['SCRIPT_NAME'];

 /* last resort - quit out and return nothing */

 } else {

  return null;

 }



 /* fint last frontslash in filename */

 $intLastSlash = strrpos($strScript, "/");



 /* check if last backslash is more far away in filename */

 if (strrpos($strScript, "\\")>$intLastSlash) {

  /* if so, use the backslash position instead */

  $intLastSlash = strrpos($strScript, "\\");

 }



 /* cut out from the last slash and to the end of the filename */

 return substr($strScript, $intLastSlash+1, strlen($strScript));

}



Tested on PHP 4.3.7/Win32 and PHP 5.0.3/Linux.

You may add more filepaths to the first if-section 

to get more chances to catch up the filename if you can.

Matt Johnson
26-Dec-2004 01:50


A reminder: if you are considering using urldecode() on a $_GET variable, DON'T!



Evil PHP:



<?php

# BAD CODE! DO NOT USE!

$term = urldecode($_GET['sterm']);

?>



Good PHP:



<?php

$term = $_GET['sterm'];

?>



The webserver will arrange for $_GET to have been urldecoded once already by the time it reaches you!



Using urldecode() on $_GET can lead to extreme badness, PARTICULARLY when you are assuming "magic quotes" on GET is protecting you against quoting.



Hint: script.php?sterm=%2527 [...]



PHP "receives" this as %27, which your urldecode() will convert to "'" (the singlequote). This may be CATASTROPHIC when injecting into SQL or some PHP functions relying on escaped quotes -- magic quotes rightly cannot detect this and will not protect you!



This "common error" is one of the underlying causes of the Santy.A worm which affects phpBB < 2.0.11.

mrnopersonality at yahoo dot com
19-Oct-2004 05:13


Nothing about the message-body ...



You can get cookies, session variables, headers, the request-uri , the request method, etc but not the message body. You may want it sometimes when your page is to be requested with the POST method.



Maybe they should have mentioned $HTTP_RAW_POST_DATA or php://stdin

hfuecks at phppatterns dot com
06-Sep-2004 09:21


Using Apache/mod_ssl, there are further environment variables available to check for an SSL connection (can be more useful than $_SERVER['SERVER_PORT']), documented here: http://www.modssl.org/docs/2.8/ssl_reference.html#ToC25



To test whether the client connected with SSL I can use $_SERVER['HTTPS'] e.g (with redirect to secured, current URL);



<?php

if ( !isset($_SERVER['HTTPS']) || strtolower($_SERVER['HTTPS']) != 'on' ) {

    header ('Location: https://'.$_SERVER['HTTP_HOST'].$_SERVER['REQUEST_URI']);

    exit();

}

?>

boaz at babylon dot com
30-Aug-2004 04:13


You can add $_SERVER["DOCUMENT_ROOT"] to IIS by editing the Environment Variables of your Windows server (was tested on WinXP SP2).



Right click on My Computer >> Properties >> Advanced.

In the System variables click on 'New' and Type in the name field 'DOCUMENT_ROOT' and in the value field  the path to your IIS document root folder.



Don't forget to restart your Windows (IIS restart won't load the new settings).

david at grant dot org dot uk
12-May-2004 02:34


$_SERVER['DOCUMENT_ROOT'] *is* supported by IIS, although only when running PHP as an ISAPI module.

youdontmeanmuch [at] yahoo.com
06-Apr-2004 06:20


Be carful when using $_SERVER['DOCUMENT_ROOT']; in your applications where you want to distribute them to other people with different server types. It isnt always supported by the webserver (IIS).

mortoray at ecircle-ag dot com
18-Dec-2003 06:32


The RAW / uninterpreted HTTP POst information can be accessed with:

    $GLOBALS['HTTP_RAW_POST_DATA']



This is useful in cases where the post Content-Type is not something PHP understands (such as text/xml).

josh,endquote,com
04-Dec-2003 12:54


Running PHP 4.3 under IIS 5 on Windows XP, there is no $_SERVER['REQUEST_URI'] variable. This seems to fix it:



if(!isset($_SERVER['REQUEST_URI'])) {

    $_SERVER['REQUEST_URI'] = substr($_SERVER['argv'][0], strpos($_SERVER['argv'][0], ';') + 1);

}

add a note

Predefined Classes

List of Reserved Words

Last updated: Fri, 11 Apr 2008

Predefined Variables

Server variables: $_SERVER

Environment variables: $_ENV

HTTP Cookies: $_COOKIE

HTTP GET variables: $_GET

HTTP POST variables: $_POST

HTTP File upload variables: $_FILES

Request variables: $_REQUEST

Session variables: $_SESSION

Global variables: $GLOBALS

The previous error message: $php_errormsg

Raw POST data: $HTTP_RAW_POST_DATA

HTTP response headers: $http_response_header

Server variables: `$_SERVER`

Environment variables: `$_ENV`

HTTP Cookies: `$_COOKIE`

HTTP GET variables: `$_GET`

HTTP POST variables: `$_POST`

HTTP File upload variables: `$_FILES`

Request variables: `$_REQUEST`

Session variables: `$_SESSION`

Global variables: `$GLOBALS`

The previous error message: `$php_errormsg`

Raw POST data: `$HTTP_RAW_POST_DATA`

HTTP response headers: `$http_response_header`