Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ISAPI DLL deployment files needed
#6
Hi Bob. First, in BoundIP=server IP, Will only accept [server IP] connections, leave it BLANK for accept connections from all.
If you like to IW15 and IIS coexist, each one takes care of its domain/port.
If they both use the same port [80/443] use HostWildcard := hwWeak; and VirtualHostName := 'yourhostname';
IIS names are on bindings and IW15 are in VirtualHostname. You can't have the same NAME/PORT (binding/virtualhostname) registered in both.
If you use a different PORT and don't need a subdomain, use HostWildcard := hwStrong;, in this case only your IW15 can accept connections on that PORT.
Use the command to see all NAME/PORT are registered on your server.
Code:
netsh>http show servicestate [enter]

I have:
https://jnp.com.br ->static HTML pages on IIS.
https://jnp.com.br/gerencial/login.html -> ISAPI on IIS.
https://fidelidade.jnp.com.br -> IW15.
All using the same server/port and same certificate. They can coexist perfectly.
Reply


Messages In This Thread
ISAPI DLL deployment files needed - by bob9999 - 12-07-2018, 06:16 PM
RE: ISAPI DLL deployment files needed - by Jose Nilton Pace - 12-09-2018, 11:45 AM
RE: ISAPI DLL deployment files needed - by joel - 12-15-2018, 01:58 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)