IIS version remove

• The errorMode="DetailedLocalOnly" setting ensures that detailed error messages are only shown on the local machine, not to external users.
• The removeServerHeader="true" setting removes the Server header from HTTP responses.

To remove the IIS version information from error responses (like 500 or 400 errors) in ASP.NET, you can utilize the web.config file to configure the section. This allows customization of error pages and helps in preventing detailed error information from being disclosed to clients.

To prevent IIS from displaying its version number in error responses (like 500 or 400 errors) in ASP.NET applications, you can modify the httpErrors section in your web.config file.

Here's an example of how you can achieve this:

1. Open your ASP.NET project's web.config file.

2. Locate the section within web.config.

3. Add or modify the httpErrors section to customize error handling and remove server information.

1. Replace /Error500.aspx with the appropriate URL of your custom error page for the respective error codes.

2. Ensure that you have an appropriate error page (Error500.aspx, for example) in your project to redirect to when these errors occur.

By configuring the httpErrors section in your web.config file as shown above, you can define custom error handling for specific HTTP status codes and prevent IIS from exposing its version information in error responses.

Remember to test these changes thoroughly in a development environment before applying them to a production environment.

To remove the IIS version from the error pages in ASP.NET when encountering 500 and 400 errors, you can modify the web.config file of your ASP.NET application.

First, locate the web.config file in the root directory of your application. Open the file in a text editor and add the following configuration settings within the  section:

In the above example, we are specifying custom error pages for both 500 and 400 errors. You can replace the /Error/ServerError and /Error/BadRequest paths with the actual paths to your custom error pages.

Next, create the custom error pages in your ASP.NET application. For example, you can create a folder named "Error" in the root directory and add the following files:

• ServerError.cshtml (for handling 500 errors)
• BadRequest.cshtml (for handling 400 errors)

In these custom error pages, you can display a user-friendly message without revealing the IIS version.

By following these steps, you can remove the IIS version from the error pages in ASP.NET when encountering 500 and 400 errors.

I assume you would like to remove IIS while you are running your .net application. Remove highlighted part in launchsettings in your application. I hope it helps