IIS 301 redirection error address followed by eurl. axd

The error occurs when ASP. NET detects that the Web site is configured to use ASP. NET 4.0, local ASP. the component of NET 4.0 will pass a URL that cannot be extended to ASP. NET Management Program for further processing. However, if one is lower than ASP. NET 4.0 website configuration to use ASP. NET 2.0, when processing such a URL that cannot be extended, the URL Modification result will contain the string "eurl. axd, the modified URL will be sent to ASP.. NET 2.0 application. "Eurl. axd" cannot be recognized in ASP. NET 2.0. Therefore, ASP. NET 2.0 will try to find a file named "eurl. axd" and execute it. Because such a file does not exist, the request will fail, an Http exception occurs, and an error with the string "eurl. axd" will be thrown.

Solution:

1. If the website program does not require the support of ASP. NET 4. 0, you can directly configure the website to use ASP. NET 2.0, and then restart the website.

2. If not. Check whether other monitoring programs are installed on the server. For example, if the IIS dongle adds the wildcard ing sequence to the IIS Site, redirection is affected. Delete the record directly.

3. Configure the redirected source site and target site. Do not use the same application pool on the same server.