Problems with FastCGI and links containing index.php? against index.php
On a Windows 2003 server running IIS 6.0 and FastCGI with a website running ExpressionEngine, I ran into an issue where links containing index.php fail if no question mark is added.
The main problem is that if the link points to "index.php / archive / article" the page will not load (see below), but it will work when "index.php? / Archive / article" is used.
What happens when the "index.php" links fail because the url will change in the browser's address bar, but the content of the main page is still displayed. Add a question mark to "index.php" and the page will load correctly.
The site previously worked with ISAPI as a server API without issue: did the server see "index.php" and "index.php?" as a synonym, and pages with "index.php" in the path will load as expected.
How do I configure a parameter somewhere that says FastCGI to handle "index.php" and "index.php?" same?
I'm a little green when it comes to Windows servers; my experience is mostly with Apache servers running in Unix boxes.
Any guidance or pointers would be most appreciated.
One option is that you can simply include the EE url query string parameter .
But if you don't like having a question mark in the url, you can try this workaround .
I can't say I don't know anything about windows servers, but this worked for me on Apache servers when running PHP as CGI. Good luck!
source to share