So if a user enters htp://example.com:8080/shop/index.php?name=abc then the Rewrite rule would check for existence of index.php and would redirect to the new location. Apache is not happy and not doing the redirect. Shall appreciate any pointers.
Thanks,
vince
jdMorgan
10:22 pm on Feb 17, 2011 (gmt 0)
Are both "ports" hosted in the same filespace, and therefore affected by this same code?
This all boils down to whether this server is defined as listening only to port 8080, or if you are simply tacking that port number onto your hostname. Both valid approaches, but handled differently ( %{SERVER_PORT} versus %{HTTP_HOST}, that is).
The query string will be "carried through" this rule by default. So there is no need to specify it in the substitution URL.
Jim
vince786
6:38 pm on Feb 18, 2011 (gmt 0)
A Big Thank You! to you Jim. The rule now works. Re your question of the 2 ports being hosted on the same file space, my answer is probably no (I will look into to confirm 100%). The port 10080 is advertised to the public entering into the system whereas underneath the post is 8080. Without the rule a user using port 8080 and the uri would be rejected by the authentication system.