REST - internal network

Markus Freitag 3,521 Reputation points
2023-11-03T19:08:52.21+00:00

Hello,

C:\Users\freitag\source\repos\WebApplicationWebanwendungFramework\Server

C:\Users\freitag\source\repos\WebApplicationWebanwendungFramework\**.vs**\WebApplicationWebanwendungFramework\config\applicationhost.config

My internal network

Is that possible 192.168.172.*

<bindings>
	<binding protocol="http" bindingInformation="*:51404:localhost" />
	<binding protocol="https" bindingInformation="*:44367:localhost" />
	<binding protocol="http" bindingInformation="*:51404:127.0.0.1" />
	<binding protocol="https" bindingInformation="*:44367:127.0.0.1" />
	
	<binding protocol="https" bindingInformation="*:44367:168.172.*" />
</bindings>
		

Could all devices then connect? I could easily use this as a test server / mock server.

ASP.NET
ASP.NET
A set of technologies in the .NET Framework for building web applications and XML web services.
1,722 questions
C#
C#
An object-oriented and type-safe programming language that has its roots in the C family of languages and includes support for component-oriented programming.
9,481 questions
0 comments No comments
{count} votes

Accepted answer
  1. Bruce (SqlWork.com) 48,711 Reputation points
    2023-11-03T20:20:13.2766667+00:00

    no. 192.168.172.* is not a valid host name, which should be a computer name or dns entry. IIS 10 added support for wildcard prefix (ex: *.mysite.com)

    you probably just want:

    <bindings>
    	<binding protocol="http" bindingInformation="*:51404:" />
    	<binding protocol="https" bindingInformation="*:44367:" />
    </bindings>
    

    note: this ports are not typically open, so you will need to change your firewall rules

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful