• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1044
  • Last Modified:

PHP Environment Variables when moving website from Unix/Apache to Windows/IIS

I'm trying to port an existing website from a Unix/Apache shared hosting environment (hosted on fluidhosting.com) to a Windows/IIS 7 shared hosting environment (hosted on aplus.net). How would I go about translating the following .htaccess file contents:

SetEnv XML_PARSER_CLASS /hsphere/local/home2/cpacweb/lib/GreenTree/Util/XMLParser.php
SetEnv CONFIG_CLASS /hsphere/local/home2/cpacweb/lib/GreenTree/Util/Config.php
SetEnv CONFIG_FILE /hsphere/local/home2/cpacweb/etc/production.xml

Specifically, I'm looking for the steps to properly set the above environment variables, which are referenced on nearly every webpage on the website. Based off my website directory configuration, I think I can correctly replace the "/hsphere/local ..." with "D:\inetpub\virtual ... \wwwroot" location.

In the UNIX environment, doing a "echo getenv('XML_PARSER_CLASS');" would output a string. Doing it in the Windows environment outputs nothing.

The attached phpinfo.pdf file contains information for the Windows/IIS environment.
  • 3
  • 2
1 Solution
On Windows, use $_SERVER instead
satellitea105Author Commented:
Thanks for the information. However, where I would place the $_SERVER variables such that it would be seen from every single webpage?

In other words, the following exists everywhere in my code:


Where would I place the $_SERVER so that every single .php file would see that the XML_PARSER_CLASS variable = '/hsphere/local/home2/cpacweb/lib/GreenTree/Util/XMLParser.php'?
Unfortunately, from my research, there is no equivalent on IIS unless you install a 3rd party module. For example: http://www.helicontech.com/ape/doc/mod_env.htm and for this you either need admin rights to the server or you need to get the admin to install it.

Without this you are probably talking about a lot or work modifying the scripts so that they will work cross platform. There are many things that work on Apache that to not work on IIS. Another example is the server variable $_SERVER['DOCUMENT_ROOT']. This does not exist on IIS and you must use an alternate means to obtain the value.
Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

@ Hube02
the author meant to use Apache on Win

@ satellitea105
instead getenv('XML_PARSER_CLASS') did you try this $_SERVER['XML_PARSER_CLASS'] ?
>>> I'm trying to port an existing website from a Unix/Apache ....... to a Windows/IIS 7 ....... <<<<

I think I got that.

The goal is to not rewrite all of the script so that they can continue to use:


If you are suggesting this:

$_SERVER['XML_PARSER_CLASS'] = 'some value here';

this does not work, this simple test shows this:

      $_SERVER['XML_PARSER_CLASS'] = 'test';
      echo '('.getenv('XML_PARSER_CLASS').')';

The above will echo an empty set of parenthesis ()

This means that he would need to call a configuration script to set the server variable and then edit all instances where the getenv.... is used to get that value set using $_SERVER

the .htaccess method does this without the need to call a configuration file, it simply make the value available.

Another possibility might be to use a configuration file to set environment variables:

      echo '('.getenv('XML_PARSER_CLASS').')';

This works, but will still require calling the configuration file from every page of the site thus needing to edit every page on the site. However, depending on php.ini settings, this could fail as well if safe_mode is set to on (which is the case on many shared hosting environments. The following is a snippet from php.ini:

; Setting certain environment variables may be a potential security breach.
; This directive contains a comma-delimited list of prefixes.  In Safe Mode,
; the user may only alter environment variables whose names begin with the
; prefixes supplied here.  By default, users will only be able to set
; environment variables that begin with PHP_ (e.g. PHP_FOO=BAR).
; Note:  If this directive is empty, PHP will let the user modify ANY
; environment variable!
safe_mode_allowed_env_vars = PHP_

The .htaccess method is like a global configuration and makes it possible to not need to set these variables withing PHP iteslf or to call configuration script to do the work, and will work no matter what the setting in php.ini.


Just out of curiosity, what path did you decide to take.

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now