ku4eto's questions

The setup is as follows:

Windows Server 2022 Standard with IIS 10.

ASP .NET 4.8 based application, running with Integrated mode and Application Pool Identity.

Im trying to remove the following headers:

Server , X-Powered-By, X-ASPNet-Version, X-ASPNetMVC-Version.

No matter what is done, the headers remain.

Things tried:

1. Remove on server level from RESPONSE HEADERS the X-Powered-By header - no effect, still shows up on dynamic content.

2. Set enableVersionHeader in server applicationhost.config configuration file and in application configuration file with no effect:

<configuration>
  <system.web>
    <httpRuntime enableVersionHeader="false" />
  </system.web>
</configuration>

3. Set on server level with no effect:

<configuration>
  <system.webServer>
    <security>
      <requestFiltering removeServerHeader="true" />
    </security>
  </system.webServer>
</configuration>

4. Set the DisableServerHeader DWORD registry value to 1 and restarted IIS with no effect: HKLM\SYSTEM\CurrentControlSet\Services\HTTP\Parameters!DisableServerHeader

5. Tried modifying the Global.asax to remove the ASPNetMVC header, but it broke the application.

I confirmed, that the changes on server level go down to the website level. I tried setting it up also manually in the web.config on the site. Same effect (none).

URL Scan is no longer available, so it is not an option. Last option seems to be to use URL Rewrite, but I would rather not use it if possible, given there are supposedly native solutions for that.

What am I doing wrong and is there something I am missing?

I have tried searching for an answer to this, but to no avail.

What is considered a best practice in a scenario, where you would need to add a 2nd IP address, from a different address range to a machine? Network ranges for example are:

Range 1 - public IP.

Range 2 - private IP.

The ranges have routing in between them.

And the methods are:

Option A: You already have 1 NIC added, using IP from Range 1, so you just add the 2nd IP address to it, aliasing it.

Option B: You add a 2nd NIC to the machine, and bind the 2nd IP address to it.

I have been left under the impression, that Option B is considered a better option, but no actual information on why so.

PS: We are assuming virtual environment, so physical NICs/slots and such are not involved.