I used IE to try to get into our clients' Outlook Web Access, and was frozen in place until I hit ESC to stop loading forever. No error codes came in. I used Firefox to do the same thing, and Firefox kicked me out with the following error: The page isn't redirecting properly Firefox has detected...

Hi all, Must be a known issue, but didn't find any solution to my problem yet. For months Google was not redirecting or reindexing my content correctly and FINALLY I found out that FastCGI on my IIS6 (W2003) is wrongly sending other PHP header redirects then I actually do. Like a 301 turns into 302...

We have been successfully using ARR in our dev and test environments for some time and have had great success. There is one key difference in our production environment that is causing some issues. We have several instances of the app running in vdirs on the same web servers. In dev and test environments...

my upper solution all of a sudden stopped working :s any info? windows7 updates? anything?

Hi, 301 Redirect is our own attemt of solving the problem. There's no result but extra one redirect. Now we disabled this rule in the UrlRewrite module. The code of the page http://85.21.218.136/index.php is <? header("HTTP/1.1 301 Moved Permanently"); header("Location: http://rarus...

If all the redirections are withing the same domain docs.win1002.vs.domain.co.uk, then there is no need to have the conditions. The rule would look similar to below: <rewrite> <rules> <rule name="Redirect" stopProcessing="true"> <match url="^$" />...

We can't do this with IIS urlrewrite! We have the PHP-array of the rules, that has urls of old and new destinations. P.S. And the question was why we can't do 301 redirect by use of PHP. We found, that after working of FastCGIModule 301 Status is turned to 302. Is it FastCGIModule's bug?

Hello. We have the web-server with Windows 2008 Server + IIS 7 + php 5.2.11 installed. The problem is, that when we attempt to redirect with 301 status, 302 status is received by client. PHP-code: header("HTTP/1.1 301 Moved Permanently"); header("Location: $new_path"); We have tried...

I've defined these rules for an .htaccess file and planned to import them onto our IIS server using the URL Rewrite Module, but it doesn't seem to do anything. Can anyone tell me if there is an obvious mistake? Original HTACCESS Options All -Indexes -MultiViews RewriteEngine on # Externally redirect...

URL Rewrite is cache friendly, meaning that for frequently hit URLs the redirection will happen really fast, a hashtable look up and then a native Redirect call. Expect great performance.