Hello again,
I have found the issue. It is in the TCP proxy we have for HTTPS tunnel.
What should be the algorithm for a full duplex TCP tunnel? I tried
pausing/resuming for not having too much buffering but it seems there is a
bug
Best Regards,
SZ
On Sun, Oct 9, 2011 at 12:25, Fastream Technologies ga...@fastream.comwrote:
Hello Arno,
Did you test with _my_ defines:
NO_STRICT;NOFORMS;NO_DEBUG_LOG;USE_SSL;SECURITY_WIN32;NO_ADV_MT;NO_ADVANCED_HTTP_CLIENT_FEATURES
Please tell me your IP number to add to our proxy server firewall which
works perfectly with IE, FF and Chrome.
Best Regards,
SZ
-- Forwarded message --
From: Arno Garrels arno.garr...@gmx.de
Date: Sun, Oct 9, 2011 at 12:08
Subject: Re: [twsocket] Cannot get TSslHttpCli to work with proxy for HTTPS
pages
To: ICS support mailing twsocket@elists.org
Fastream Technologies wrote:
Hello,
I have a working proxy server which I want TSslHttpCli to connect via
CONNECT and then connect via HTTPS in tunnel. It corrupts the FPath
such that there is now two domains and two ports in URL sent to web
server. I can reproduce this with ICS demo too. I can provide access
to my proxy server if you can tell me your IPs.
I cannot reproduce, however I found another little bug with squid proxy
and checked in the change I suggested last week.
Log: - Clear FResponseVer after relocations when the connection was
closed.
This ensures that ProxyConnection keep-alive is set on proxy-reconnects
after relocation with HTTPS as well.
- Made a change in GetHeaderLineNext to fix a bug with 401 and 407
responses when no content-length header was present (body was parsed as
header, thanks to Fastream for reporting).
--
Arno Garrels
--
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
