Force10x - 3:23 am on Oct 21, 2013 (gmt 0)
Apologies for resurrecting this thread.
These Redirect rules work well when I run them on my local development server.
However, when I run them on the production server they give a 404 error instead of triggering the redirects.
It took me a while to figure out that it could be due to the "proxy" server (web server sitting between the client and the actual CMS app server).
Seems like the proxy module gets hold of the URL first pushes it off the server which promptly sends back the wrong response i.e. 404.
I need the rewrite to occur first, then the new URL submitted and passed through to the proxy.
Then again I may be wrong.
In this scenario, should the rewrite rules still work irrespective of the "proxy"?