|
|
 |
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).
As of PHP 5.0.0, the long PHP
predefined variable
arrays may be disabled with the
register_long_arrays
directive.
Note:
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 webserver. There is no guarantee that
every webserver 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 an autoglobal. (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 autoglobals.
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_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'.
Note:
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.
- '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.
Note:
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.
Note:
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.
Note:
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.
Note:
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 an autoglobal. (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 autoglobals.
Note:
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 an autoglobal. (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 autoglobals.
Note:
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 an autoglobal. (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 autoglobals.
Note:
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 an autoglobal. (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 autoglobals.
Note:
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 an autoglobal. (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 autoglobals.
Note:
Introduced in 4.1.0. There is no equivalent array in earlier
versions.
Note:
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 autoglobals.
Note:
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 an autoglobal. (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 autoglobals.
Note:
$GLOBALS has been available since PHP 3.0.0.
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.
$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).
User Contributed Notes
Predefined Variables
sienkiewicz at gmail dot com
19-May-2005 09:18
Here is a very simple method of extracting all $_GET variables in a URL. This is useful when working with dynamic reports, that may need to be sorted, etc.
code:
foreach($_GET as $variable => $value) {
echo "Variable Name: " . $variable . " Value: $value<br>";
}
www dot php dot net at webdevelopers dot cz
12-May-2005 08:01
Simple function that selects "best" language for the user from the list of available languages:
function chooseLang($availableLangs) {
$pref=array();
foreach(split(',', $_SERVER["HTTP_ACCEPT_LANGUAGE"]) as $lang) {
if (preg_match('/^([a-z]+).*?(?:;q=([0-9.]+))?/i', $lang.';q=1.0', $split)) {
$pref[sprintf("%f%d", $split[2], rand(0,9999))]=strtolower($split[1]);
}
}
krsort($pref);
return array_shift(array_merge(array_intersect($pref, $availableLangs), $availableLangs));
}
echo 'BESTLANG: '.chooseLang(array('cs', 'sk', 'ru', 'en'));
Daniel "elixon" Sevcik
07-May-2005 01:32
To display the url of a page (like the one in the address bar)
you can use this script:
<?php
echo "http://";
echo $_SERVER['HTTP_HOST']; echo $_SERVER['REQUEST_URI']; ?>
This could be used in a login script to redirect the user back to the page they logged in from instead of the index
exaton at free dot fr
06-May-2005 01: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 08: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.
javalizard at mac dot com
10-Apr-2005 06:02
My web host server will give my php the user preferred languages out over the order. This means that I had to write a function for ordering the languages based upon their "q" value (rank from 1..0, 1 being the most preferred). If you want an ordered list of user preferred languages use this function:
<?php
function orderedLanguages()
{
$languages = split(",", $_SERVER['HTTP_ACCEPT_LANGUAGE'] );
$lang_q = Array();
foreach( $languages as $aLang ) {
$lang_array = split(";q=", trim( $aLang ) );
$lang = trim( $lang_array[0] );
if( !isset( $lang_array[1] ) )
$q = 1;
else
$q = trim($lang_array[1]);
$lang_q["$lang"] = (float)$q;
}
arsort($lang_q);
$i = 0;
$lang_index = Array();
foreach($lang_q as $lang => $q) {
$lang_index[$i] = $lang; $i++;
}
return $lang_q;
}
?>
While you can't reference the key by number, You can use foreach to pull elements. This will be in order. So getting the key with array_keys should work in the preferred order too. I've added a few extra lines of commented code for reordering the array into one(s) that reference the language by number (if you need it) :D
skrollster
26-Mar-2005 10:36
$_SERVER["REMOTE_USER"] and $_SERVER['PHP_AUTH_USER'] is the same variable i think..
anonymous
04-Mar-2005 04:12
I don't see the $_SERVER["REMOTE_USER"] listed in this document.
This displays the username used to login using .htaccess.
z dot stolar at gmail dot com
02-Mar-2005 04:05
It seems that if the current page was called with GET variables:
http://www.example.com/index.php?delete_id=12?add_id=34
and if, in that same page, you are about to submit another form, this time with POST method, assigning the form the action:
<?php $_SERVER['PHP_SELF'] ?>
will keep the GET variables at their place! (delete_id=12?add_id=34)
Rather, assign the form the action like this:
<?php echo $_SERVER['PHP_SELF'] ; ?>
this will call only index.php without any GET variables
27-Feb-2005 08: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.
x_terminat_or_3 at [remove] yahoo.fr
27-Feb-2005 04:18
I didn't find it anywhere here and I was ready to bang my head on the wall until I found the solution!
So when you use a select with multiple options you have to cheat to let php recognize it.
When processing the request, php puts all selected options in the select object's name, but treats it like an array. If it is not an array, only the last option is remembered.
So to cheat you should append [ ] to the name of the select
<form .. ... ..>
<select multiple="multiple" name="myselect[]" size="3">
<option value="1">1st option</option>
<option value="2">2nd option</option>
<option value="3">3rd option</option>
...
Then in the processing part:
<?php
if(!empty[$_REQUEST['myselect']) print_r($_REQUEST['myselect']);
?>
Will show you the array with all the selected options
17-Feb-2005 05:30
grlprgrmmr wrote:
you can use these to reconstructed the current page url.
<?php
echo 'http';
if($_SERVER['HTTPS']=='on'){echo 's';}
echo '://'.$_SERVER['SERVER_PORT'].$_SERVER['SCRIPT_NAME'];
if($_SERVER['QUERY_STRING']>' '){echo '?'.$_SERVER['QUERY_STRING'];}
?>
______________
the $_SERVER['SERVER_PORT'] part should be changed to $_SERVER['HTTP_HOST']
Gregory Boshoff
13-Feb-2005 06: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
11-Feb-2005 09: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.
grlprgrmmr uses gmail
10-Feb-2005 01:05
you can use these to reconstructed the current page url.
<?php
echo 'http';
if($_SERVER['HTTPS']=='on'){echo 's';}
echo '://'.$_SERVER['SERVER_PORT'].$_SERVER['SCRIPT_NAME'];
if($_SERVER['QUERY_STRING']>' '){echo '?'.$_SERVER['QUERY_STRING'];}
?>
If $_SERVER['HTTPS']=='on' does not work for you,
try $_SERVER['SERVER_PORT']==443 (or whatever secure port is used)
JSP001
27-Jan-2005 04:15
Hi dotpointer,
I am new to php but I suggest a little modification of your script. Tell me what you think of it :
function getThisFile() {
[...]
/* last resort __FILE__ */
} else {
$strScript = __FILE__;
}
[...]
}
Thanks for this great function, I'll use it for my project !
Regards
niles AT atheos DOT net
26-Jan-2005 02: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
23-Jan-2005 06:02
The variable $php_errormsg is not populated if you have XDebug running.
arjini at gmail dot com
18-Jan-2005 06:29
roy dot rico at gmail dot com
18-Jan-2005 03:48
if you are trying to use $php_errormsg, it acts more like a function than it does a variable.
example
echo "<h1>";
$php_errormsg;
echo "</h1>";
will output:
<h1>[the php error]<h1>
however, this command
echo "<h1>" . $php_errormsg . "</h1>";
should produce the same thing, yet it produces
[the php error]<h1></h1>
not sure if this is a "feature" or a "bug"
dotpointer
09-Jan-2005 03: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
25-Dec-2004 06:50
A reminder: if you are considering using urldecode() on a $_GET variable, DON'T!
Evil PHP:
<?php
$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 10: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 02: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 09: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 07:34
$_SERVER['DOCUMENT_ROOT'] *is* supported by IIS, although only when running PHP as an ISAPI module.
youdontmeanmuch [at] yahoo.com
05-Apr-2004 11: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 11: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
03-Dec-2003 05: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);
}
| |