awarnier wrote: > > Chris Graham wrote: >> One other suggestion was to do this: >> >> RedirectMatch Permanent /(.*) http://hudson.warpspeed.com.au/hudson/$1 >> >> However, that ends up with the infinite loop as well. :-( >> > Yes. > What probably happens is : > - a request comes in for / (or /x..) > - it gets caught by the redirect rule, and a 302 (moved) response is > sent back to the browser, indicating a new address of > http://hudson.warpspeed.com.au/hudson/ (or ../hudson/x..) > - the browser immediately and transparently sends back a request for > /hudson/ > - this request is caught by the same redirect rule, results in a new 302 > (moved) response, with an address this time of > http://hudson.warpspeed.com.au/hudson/hudson/ > - and so on for ever > > It would not matter if the server to which your redirect sends the > request was not the same as this one. But since here it is the same, > you loop infinitely. > So is this a bug (as it worked as I need it to in 1.3), or just an incompatable change? [or a bug that's been fixed from 1.3?] I'll look into the rewrite stuff. Thanks for your help. -Chris -- View this message in context: http://www.nabble.com/Redirect-Issues-%28Migrating-from-1.3-to-2.0%29-tp20880100p20906991.html Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|