What I tried to explain to you is the simplest method--if the client is in
the same computer and if it uses 127.0.0.1 as the destination addess, then
the source address from server's point of view must be 127.0.0.1 as well..
So if you use the listening IP as 127.0.0.1, then no other IP would be able
to connect, which was your goal.
For HTTP(S) authentication, you have 5 options:
1) HTTP/1.0 basic auth
2) HTTP/1.1 digest auth which is somewhat secure
3) NTLM, the securest yet the credentials-to-compare are out of your
control, they are taken from Windows
4) GET param
5) POST data
We support all except 4) implicitly in IQ Reverse Proxy:
On 12/4/07, Arno Garrels <[EMAIL PROTECTED]> wrote:
> Hoby Smith wrote:
> [Big snip]
> > For example, you could use, TMyHttpConnection(Client).GetPeerAddr, to
> > get the client's address and then determine if you want to disconnect
> > it. You would have to provide this logic and any rules as you need.
> There are helper functions available in OverbyteIcsWinsock2.pas to get
> the list of interfaces including loopback and also a function to check
> whether an IP is in current subnet.
> Arno Garrels
> [Big snip]
> To unsubscribe or change your settings for TWSocket mailing list
> please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
> Visit our website at http://www.overbyte.be
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be