Interface displays Bad Request (Invalid Hostname) HTTP Error 400. The request hostname is invalid. Solution

       A lot of people after the configured IIS server, open your site is indeed return Bad Request error. The main reason that led to this error is that the domain name has been resolved, but the hosts could not find a corresponding domain name.

        When setting up the site identifier, typically the server IP to "All Unassigned" (shown below), then you can guarantee to resolve any IP server bindings can access to the WEB service. This is appropriate when multiple network cards in the server configuration, usually an IP, or even multiple network adapters, also need to specify the exact IP, to facilitate the management and ongoing maintenance. Hostname recommended setting is empty, if the host name is set incorrectly formatted agree easily lead to not visit the site you want.

Appear Bad Request (Invalid Hostname) one error, when the IP to the specified IP, and the server bind multiple IP addresses, use a different IP address when accessing that error.

At this solution, the IP is set to "All Unassigned" longer accessible. DETAILED IP settings specific steps:

Find IIS Manager - find the corresponding website - right click - binding site - Edit Site Binding - be determined

         Specific operation is as follows screenshot

           Next:

 

Guess you like

Origin www.cnblogs.com/TechSingularity/p/11777046.html