Re: [twsocket] Problem with Proxy Port with HttpTest

2005-09-17 Thread Francois PIETTE
In THttpCli.SendRequest, try this fix (FTargetPort instead of FPort): if FTargetPort = '80' then Headers.Add('Host: ' + FTargetHost) else Headers.Add('Host: ' + FTargetHost + ':' + FTargetPort); Contribute to the SSL Effort. Visit http://www.overbyte.be/eng

Re: [twsocket] abnormal winsock behaviour by firewall

2005-09-17 Thread Steve Endicott
We have a program that contacts our web site for information (standard http request). Sometimes, one of our users will not be paying attention and will allow Norton Internet Security to block our application. In the past, Norton would return a 10061 (connection refused) error which made sense

Re: [twsocket] SocksServer. Host name resolving.

2005-09-17 Thread Francois PIETTE
Only socks5 does name resolution for the client. -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: "asvetov" <[EMAIL PROTECTED]> To: Sent: Friday, September 16, 2005 11:15 PM Subject: [twsocket] SocksServer. Host name resolving. > Hello all! > > Using TWSocket, whe

Re: [twsocket] abnormal winsock behaviour by firewall

2005-09-17 Thread Francois PIETTE
> Norton let's you connect without error which is very abnormal, > so I hereby clasify the product as 'not good' :) I share your opinion. I frequently have ICS user contacting me because they heve problems with their application. It happend frequently that Norton security product is the culprit.