[wp-hackers] ISAPI_Rewrite 3.0 mod_rewrite compatibility

[Computer Guru]

Yes, I just checked a couple of days ago with the latest SVN.

Request_URI will still return index.php, which is script_name...

This is the most reliable workaround I've seen. It's part of my "Request_URI
for Windows" package as a fallback if ISAPI_Rewrite isn't installed:


if(isset($_SERVER['SCRIPT_NAME']))

$_SERVER['HTTP_REQUEST_URI'] = $_SERVER['SCRIPT_NAME'];

else

$_SERVER['HTTP_REQUEST_URI'] = $_SERVER['PHP_SELF'];

if($_SERVER['QUERY_STRING']){

$_SERVER['HTTP_REQUEST_URI'] .= '?' . $_SERVER['QUERY_STRING'];

}

$_SERVER['REQUEST_URI'] = $_SERVER['HTTP_REQUEST_URI'];
Only thing is, if anyone is using a hack (like mine) to set REQUEST_URI to
the correct value, it'll overwrite it.

On 9/17/07, Mark Jaquith <mark.wordpress at txfx.net> wrote:
>
> On Sep 15, 2007, at 7:09 PM, Computer Guru wrote:
>
> > Note that the stupid Windows/IIS request_uri bug still exists, you'll
> > need to use this IIS hack [2] to make WP correctly grab the
> > request_uri value.
>
> Is that true, even with WP 2.3 beta code?
>
> --
> Mark Jaquith
> http://markjaquith.com/
>
> Covered Web Services
> http://coveredwebservices.com/
>
> WordPress Ninja @ b5media Inc
> http://b5media.com/
>
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>



-- 
Computer Guru
Director,
NeoSmart Technologies
http://neosmart.net/blog/