Bad Request - Invalid Hostname when accessing localhost Web API or Web App from across LAN
IIS Express does not allow remote connections by default. This post explains how to activate it.
In my opinion, you would be better off if you setup local IIS and publish the app to the configured IIS folder.
I already tried HTTP.SYS configurations for other situations, and sometimes the configs are lost whether on restarts or windows updates... But this may not happen to you...
Related videos on Youtube

Fabricio Rodriguez
I'm a software developer based in Pretoria, South Africa. I develop in C# / .Net (mainly WinForms, WPF and .Net Core Web API) and have recently started learning Angular.
Updated on September 10, 2021Comments
-
Fabricio Rodriguez over 1 year
I have an ASP .Net Core 1.1 Web API and Web App running on my localhost from Visual Studio 2017 on Windows 10.
When I run the projects, the API runs on http://localhost:50082/api/ and the web app on http://localhost:60856/
However, if others on the LAN try to access it (using my computer's IP address - http://192.168.1.101:60856/ they get a
Bad Request - Invalid Hostname
Error. In fact,. I get this error too of I use my IP address. I've tried about a dozen variations in my C:\Users\Documents\IISExpress\config\applicationhost.config file, such as:
<bindings> <binding protocol="http" bindingInformation="*:60856:localhost" /> </bindings>
and
<bindings> <binding protocol="http" bindingInformation="*:60856:" /> </bindings>
restarting the projects (and therefore IIS Express) every time, but nothing seems to work. Any ideas?
-
Fabricio Rodriguez over 5 yearsThanks, the free VS extension from visualstudiogallery.msdn.microsoft.com/ worked wonders
-
Jim W says reinstate Monica over 4 yearsHere's the direct link to the extension marketplace.visualstudio.com/…