Rewrites happen internally within IIS. The HTTP request is intercepted very early in the pipeline processing request and then transformed into a the re-written URL and passed deeper into the pipeline to whatever handler is processing the request.
1. old and new site need to be on the same box obviously. 2. the user agent is never made aware of the rewrite because it all happens server side. This is why you don't see the address change. You need to do a *redirect *with a permanent (301) response code. Also, if you're using Internet Explorer, keep in mind it is a piece of sh1t and will randomly not update the address bar for whatever reason even during a redirect. On Wed, 27 Jul 2016 at 14:56 Greg Keogh <[email protected]> wrote: > can you see what the network is doing? you dont need fiddler u can just >> use chrome: as an example type 'google.com' into the browser and then >> the first response is a 302 >> > > I don't use Chrome, but I had a look in Fiddler anyway and it produces no > clues, just a 404 response. > > I was told earlier today that "oldsite" is deprecated, so I used a > *rewrite* rule to send everyone at oldsite to a html page with links and > comments about "newsite". After more stuffing around I found that an IIS > URL Rewrite *rewrite* rule works, but all *redirect* rules are ignored, > which is a separate unsolved problem. > > So I didn't solve the original problem, it's just gone away. > > *GK* > -- David Connors [email protected] | @davidconnors | LinkedIn | +61 417 189 363
