I’ve changed the custom 404/405 error page from /index.php to the default IIS files.
I put the httpd.ini file back in the web root with the same code as is noted in my previous post.
With this setup no URL rewriting is happening on the website so I was a little confused about how it is meant to be set up.
In IIS on the ISAPI_Rewrite tab the config line reads: C:\Inetpub\vhosts\cubeit.co.uk\subdomains\modx103\httpdocs\.htaccess
I renamed httpd.ini to .htaccess on the server, refreshed the website and URL Rewriting is working as are form posts.
So I guess I’ve now achieved the setup you advise running with and I’ll need to get my $95 out ;p
The thing I really don’t understand from the previous setup is why Google et al would see a 404 Not Found when Firebug was showing 200 OK. I know the Form POST rebuild thing was a hack and hacks are not fixes.
Thanks again.
-
☆ A M B ☆
- 711 Posts
Hi Chris,
That’s awesome that you have fixed it I was just about to reply saying ISAPI Rewrite v3 expects .htaccess but you found that out.
Regarding the 200 / 404 messages in firebug check out the plugin HTTPFox for firefox.
Now that you know ISAPI Rewrite is doing it’s job you should now turn on custom error 404 to point to /index.php this is so that it can purely process 404’s and have MODx show a 404 page, but in the background it will tell the browser it was a 404 and log that information in your web stats.
Thanks Aaron
Aaron, you are a genius. Thanks again for your help on this.
Chris.
-
☆ A M B ☆
- 711 Posts
No problem at all just glad to see another happy Windows Server running MODx
If you run into any more problems running MODx on Windows just let me know.
Thanks Aaron