Xitami on Microsoft Windows

This section contains notes and hints specific to » Xitami on Windows.

Note:

You should read the manual installation steps first!

This list describes how to set up the PHP CGI binary to work with Xitami on Windows.

Note: Important for CGI users

Read the faq on cgi.force_redirect for important details. This directive needs to be set to 0. If you want to use $_SERVER['PHP_SELF'] you have to enable the cgi.fix_pathinfo directive.

Warning

A server deployed in CGI mode is open to several possible vulnerabilities. Please read our CGI security section to learn how to defend yourself from such attacks.

  • Make sure the web server is running, and point your browser to xitamis admin console (usually http://127.0.0.1/admin), and click on Configuration.

  • Navigate to the Filters, and put the extension which PHP should parse (i.e. .php) into the field File extensions (.xxx).

  • In Filter command or script put the path and name of your PHP CGI executable i.e. C:\php\php.exe for PHP 4, or C:\php\php-cgi.exe for PHP 5.

  • Press the 'Save' icon.

  • Restart the server to reflect changes.

add a note add a note

User Contributed Notes 8 notes

up
0
Alex
17 years ago
I used php v 5.1.4 and the latest Xitami version.

1st change, use 'C:\php\php-win.exe' (in Windows OS) instead of 'C:\php\php-cgi.exe'

2nd change, you must click on the save button after you have changed the filters page and then again in the standarn configuration page.

finally, restart the server by going to the windows Gui interface (right click on the Xitami symbol in the system tray and choose properties) and click suspend (so the background for the 'X' goes red) then click start again.

hope this helps anyone with problems
up
0
rjb1 at catalog dot net dot au
20 years ago
I am running xitami as a business www server on ms-windows. I have a number of long-running PHP scripts. I developed a tiny java applet to receive and display progressive status information from these slow scripts. It effectively facilitates SERVER PUSH from PHP scripts to IE and Netscape browsers.  Take a look: catalog.net.au/netClient.zip (Ron Boles, Melbourne, Australia)
up
0
rjb1 at catalog dot net dot au
20 years ago
PHP via ISAPI with XITAMI
I have developed a small GUI in c++, which runs XITAMI and configures the Xitami ISAPI interface for use with PHP. It is so much faster than the PHP cgi interface and appears to be more stable too.
Take a look here: http://catalog.net.au/xisapi/default.html
Ron Boles
Melbourne, Australia
up
0
Roshambo
21 years ago
I was only able to get PHP (4.3.3) working under Xitami (2.5c0) on Windows XP (SP1) by adding the following lines to defaults.cfg:

[Mime]
    php=application/x-httpd-php
   
[Filter]
    .php="c:/php/php.exe"

Note the quotation marks and the forward slashes in the filter section.
up
0
david at advisorymatters dot co dot uk
21 years ago
Using the CGI (c:\php[version]\php.exe) with Xitami since PHP version 4.3.2 requires the following setting in php.ini before the $_SERVER['PHP_SELF'] call will return a value:

cgi.fix_pathinfo=1

Note that $_SERVER['SCRIPT_NAME'] still works.
up
-1
Tom dot Cockaert at d-c-s dot be
16 years ago
I was able to get it to work with the info from Alex (
06-Jan-2007 12:22) with one addition though.

When I did the steps he mentioned I did not see anything yet in my browser.
I still had to hard refresh my page by CTRL-F5, then I finally had an output from my testscript.

Br,
Tom.
up
-1
ae_engine at yahoo dot com
19 years ago
I have successfully configured Xitami using cgi.redirect
in PHP
set cgi.redirect = 1
set cgi.redirect_status = CGI_REDIRECT_STATUS;

in Xitami, defaults.cfg
under CGI_ENVIRONMENT
insert CGI_REDIRECT_STATUS="-"
up
-1
janko dot slavic at email dot si
21 years ago
[Editors Note]
You can force IE to disregard a cached page by pressing the Control key and click the Refresh button.

Please, do not forget the IE caches files.

I had a test.php and got the error message. I changed the defaults.cfg and also the cgi.force_redirect to = 0. After restarting the Xitami the error message was still there.
After a while I saved the test.php file to test2.php and found that it is working fine...
To Top