Sorry, sent to early. Here is the rest of the text.
I got the version 706 of OverbyteIscHttpProt.pas toady.
On line 3638 and 2629 is the source of the problem.
When state is httpWaitingProxyConnect and if the answer from proxy contains 200
OK, then the process stops and nothing more happens.
My first thougt is to change these lines:
) and not
((StrLIComp(PAnsiChar(FReceiveBuffer), AnsiString('HTTP/1.1 200
OK'), 15) = 0) or
(StrLIComp(PAnsiChar(FReceiveBuffer), AnsiString('HTTP/1.0 200 OK'),
15) = 0)) then
If the proxy have an errortext to send to the client, I think the proxy sends
200 OK and a document. I think that if we add to these lines that the
content-length also have to be 0 all is fixed.
Then proxies that answers 200 OK and content-length is 0 (no error) when
connection is established will work, and when content-length is more than 0
(proxy send us a description of an error) then we don't continue to send data.
Any thoughts on this anyone?
Regards
Bjørnar Nielsen
_
From: Bjørnar Nielsen
Sent: 17. februar 2010 21:41
To: ICS support mailing
Subject: [twsocket] Bug and proposal for fix in TsslHttpCli using proxy
I have found a bug using https through proxy.
After connect-command to the the proxy it answers back to the client 200
Connection established.
I have come across some proxy-servers that answers 200 OK back to the client.
This is a problem for TsslHttpCli.
--
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
