Jump to content

StandAlone Server Binding Issues - ReVisited


andyhill

Recommended Posts

When one assigns the Port to the Server (UniServerModule.Port:= HttpPort and UniServerModule.SSL.SSLPort:= SslPort) UniGUI binds those ports to all NIC assigned IP's - this is not good.

According to the Indy People we need 2 Bindings, one for port 80 and one for port 443.
The workaround was to set UniServerModule.Port:= 0 (kill global binding), UniServerModule.SSL.SSLPort:=0 (kill global binding) and add Binding Records, then from here assign the desired IP's and Port's.

    UniServerModule.Bindings.Items[0].IP:= BindToIpStr;
    UniServerModule.Bindings.Items[0].Port:= HttpPort;

    UniServerModule.Bindings.Items[1].IP:= BindToIpStr;
    UniServerModule.Bindings.Items[1].Port:= SslPort;

Now the downfall of having UniServerModule.Port:= 0 (kill global binding) is that the only way to access the site now is via https which Indy navigates automatically, in principle this is not an issue if the user knows he must use https, if he dose not know then the http protocol will fail and he will not arrive at your site.

I have begged Farshad many many times to NOT GLOBALLY BIND ALL IP's.

Farshad, please address this problem -or- provide a work around where one can run multiple StandAlone WebServers on the same PC bound across different IP's.

 

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...