- Apr 10, 2005
- 2,131
- 21
- 81
Ok, so, this *was* working properly, then our host moved us and now it's stopped. I've got a bunch of rewrite rules going, primarily to turn the Merchant server's piss ugly urls into less hideous ones.
One of the rules is supposed to turn the nice, pretty URLs for public consumption back into the ugly ones the server actually ones. Before, a simple rewrite rule with no [R] flag accomplished this just fine. Since the switchover, however, the browsers are now actually showing the final ugly url again. I can get it running like it was by putting the [P] flag in, and for now I'm going to do this, but since this isn't actually a proxy, just an internal rewrite, I don't see why this is neccessary.
Is there some default maybe that got turned on and made all rewrites into 301/302 redirects by default, which I can somehow override in my own .htaccess?
EDIT: Nevermind. Took the http off the redirect locations and it went back to working. This really is voodoo though. Can't say I generally understand why that worked at all.
One of the rules is supposed to turn the nice, pretty URLs for public consumption back into the ugly ones the server actually ones. Before, a simple rewrite rule with no [R] flag accomplished this just fine. Since the switchover, however, the browsers are now actually showing the final ugly url again. I can get it running like it was by putting the [P] flag in, and for now I'm going to do this, but since this isn't actually a proxy, just an internal rewrite, I don't see why this is neccessary.
Is there some default maybe that got turned on and made all rewrites into 301/302 redirects by default, which I can somehow override in my own .htaccess?
EDIT: Nevermind. Took the http off the redirect locations and it went back to working. This really is voodoo though. Can't say I generally understand why that worked at all.
Facebook
Twitter