I just set up IIS under Win2K Pro as a development platform for my production website, and installed PHP. Works fine.

The problem is, my production website only has default documents set to index.htm* (since it's hosted by a third-party, and I don't have 'true' admin rights to it, I can't change it). And I need PHP processing on these "home" pages.

Rather than do some stupid redirect from index.html to index.php, I've actually been able to include php files in the html files with SSIs (&lt!--#include virtual="somefile.php" --&gt) and the PHP is processed before it's returned to the browser. Works great.

Except I can't replicate the behavior on the development platform. The PHP file gets included... but no processing takes place... so I just get a bunch of PHP source spit out.

The production site may or may not be served on UNIX... would one expect SSIs to get pre-processed on UNIX and not on Win32? If not, can anyone think of some other reason I can't get pre-processing to work on my development platform? (and, yes, I've checked a straight .PHP file and it processes... just not within an SSI).

Thoughts?

    you may have to set up apache to pre process SSI on your development server.

    if you are paying good money for hosting, just tell the hosts that you want to add index.php as one of the default index pages....... that isn't a security risk at all and i'm sure they would do it.

      Thanks Michael,
      I'll look into Apache for Win2K (??). Hopefully that's the key.

      I really actually like having all my pages be .HTML... so I'm not sure I want to change anything. Plus, if I changed everything to .php, I'd have to have a bunch of redirects from other pages that stand a high chance of having been bookmarked. Not a fun prospect.

      I'd much rather get my development box working like the production box. But if it comes down to it, I'll give my hosting co a call :-)

      Thanks again,
      -Carl

        Write a Reply...