On Thursday, January 09, 2014 6:21 PM [GMT+1=CET],
Arno Garrels wrote:
> Since it works without a proxy fine it's IMO some bug in THttpCli or
> TSslHttpCli. In both cases the HTTPS-client establishes the SSL, the
> proxy just forwards the bytes. I have no idea how to fix it at the
> moment :(
Indeed it is. The problem is that an invalid request string is sent to
the server. Field TSslHttpCli.FPath includes the entire URL when method
SendRequest() is executed. Since I do not have much spare time I just
can post a quick and dirty workaround in unit OverbyteIcsHttpProt here:
{code}
{* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *}
{$IFDEF USE_SSL}
procedure THttpCli.SslHandshakeDone(
Sender : TObject;
ErrCode : Word;
PeerCert : TX509Base;
var Disconnect : Boolean);
var
// <== added
LProto, LUser, LPass, LHost, LPort : String; // <== added
begin
[..]
if not FProxyConnected then
Exit;
ParseURL(FURL, LProto, LUser, LPass, LHost, LPort, FPath); // <== added
try
FNext := GetHeaderLineNext;
StateChange(httpWaitingHeader);
[..]
{code}
Hope that helps
--
Arno
--
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
