4873 Posts in 7242 Topics by 1471 members
|Go to End|
19 December 2008 at 4:26pm Last edited: 19 December 2008 4:28pm
We've been using the 2.2x series SS with great success on IIS /w Isapi Rewrite (v3x). Looking towards the future of SS and all the modular upgrades in the works we are looking to upgrade to the 2.3x series SS.
Considering the exact same release (12/18/2008 trunk) works perfectly fine on Apache/Linux, there must be a problem with either the ISAPI_REWRITE or IIS.
Has anyone had success in fixing or at least determining the problem at hand? I'm about to go back to tackling it now.
23 December 2008 at 5:03pm
One possible clue I've discovered is Isapi_Rewrite sends a modified REQUEST_URI (and cloned REQUEST_URL) to the web server, is this how the module tricks IIS into serving the proper page?
There are several places in the code that reference REQUEST_URI and expect it to be '/admin' and not '/sapphire/main.php?url=/admin&'
$_SERVER['REQUEST_URI'] = '/'.$url;
into the main.php in the Apache rewrite rules area when $_GET['url'] exists, didn't seem to help there, but I'd imagine it would help in other places.
8 January 2009 at 1:41pm
Can you put print_r($_SERVER); at the top of main.php, then visit the page and post its output to this forum thread? I'd like to see in more detail the values that IIS/ISAPI_REWRITE generates.
|Go to Top|