Forum Moderators: phranque
For me, my solution was to simply remove the complete url and change only the changed portion (likened to relative paths as opposed to absolute).
RewriteRule ^monitor([0-9]+) htp://same-domain/apps/docketscroller/showdocket-js2.php?monitorid=$1 [nc]becomes
RewriteRule ^monitor([0-9]+) showdocket-js2.php?monitorid=$1 [nc]
What I don't really get is why? And is there a better/another way?
1) Generate an external redirect.
2) Change the filepath associated with a requested URL -- an internal rewrite.
3) Create a proxy through-put (not relevant to this thread).
The syntax of the rule determines which of those first two it will do.
External redirect:
RewriteRule ^foo\.php$ http://www.example.com/bar.php [R-301,L]
RewriteRule ^foo\.html$ /foo.php?req=foo [L]
This may in fact be a cause of your problem. For example, if you took the [L] flags off my rules above, and then reversed their order, the redirect would 'expose' the internal rewrite.
Jim
Funny how something that's been around and documented for years, we can still hypothesize about like it's an alien mineral found in a field.
Thanks (cross-post) again for your input jdM.
-bronius