asp.net Http exception eurl.axd error message resolution
- 2020-05-12 02:30:58
- OfStack
The cause of the error is that when ASP.NET detects that the Web site is configured to use ASP.NET 4.0, the local ASP.NET 4.0 component will pass a non-extensible URL to ASP.NET hypervisor for further processing. However, if a website below ASP.NET 4.0 is configured to use ASP.NET 2.0 to handle such an unextensible URL, the modified URL result will contain the string "eurl.axd" and the modified URL will be sent to the ASP.NET 2.0 application.
"eurl.axd" is not recognized in ASP.NET 2.0. So ASP.NET 2.0 will try to find a file called "eurl.axd" and execute it. Because there is no such file, the request fails, Http exceptions are thrown and an error with the string "eurl.axd" is thrown.
There are three ways to solve this problem:
1. If the website program does not require ASP. With support for.0, you can directly configure your website to use ASP.NET 2.0.
2. If the website program requires ASP. With support for.0, you need to move the virtual directory using ASP.NET 2.0 from that site to another site.
3. If neither of the above methods is applicable to your situation, this is the only way to use it:
Open the registry and find "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\ ASP.NET \4.0.30319.0", add the key value of "EnableExtensionlessUrls" of type "DWORD" and set the value to "0". Then run "IISRESET" in cmd and restart IIS to read the registry changes. Note: this modification is to close ASP. .0 for no extension URL processing, if this key value is set to "1", it is turned on.
"eurl.axd" is not recognized in ASP.NET 2.0. So ASP.NET 2.0 will try to find a file called "eurl.axd" and execute it. Because there is no such file, the request fails, Http exceptions are thrown and an error with the string "eurl.axd" is thrown.
There are three ways to solve this problem:
1. If the website program does not require ASP. With support for.0, you can directly configure your website to use ASP.NET 2.0.
2. If the website program requires ASP. With support for.0, you need to move the virtual directory using ASP.NET 2.0 from that site to another site.
3. If neither of the above methods is applicable to your situation, this is the only way to use it:
Open the registry and find "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\ ASP.NET \4.0.30319.0", add the key value of "EnableExtensionlessUrls" of type "DWORD" and set the value to "0". Then run "IISRESET" in cmd and restart IIS to read the registry changes. Note: this modification is to close ASP. .0 for no extension URL processing, if this key value is set to "1", it is turned on.