What does TCustomSslWSocket derive from?
On 12/9/06, Jack <[EMAIL PROTECTED]> wrote:
> Hello Arno,
>
> If you have tested it, I could be wrong. I didn't actually test it.
> I just looked at the code below and it seems that SSL and Socks are
> mutually exclusive. I didn't dig it further.
>
> {$IFDEF USE_SSL} { Makes the IDE happy }
> TBaseParentWSocket = TCustomSslWSocket;
> {$ELSE}
> TBaseParentWSocket = TCustomSocksWSocket;
> {$ENDIF}
>
> --
> Best regards,
> Jack
>
> Saturday, December 9, 2006, 9:59:17 AM, you wrote:
>
> > Hello Jack,
>
> > [..]
> >> - socks and SSL support in existing ICS code is not done in the ideal
> >> way. As it is now, a socket is either an SSL socket or a socks
> >> socket. An SSL connection should also also be able to go through a
> >> proxy server, but not with the current code.
>
> > Hmm, this worked fine in the past, but I have not tested Socks with SSL
> > since
> > a long time, so changes in the SSL code since that time may have broken it,
> > if you say that Socks with SSL doesn't work in current versions I will
> > reactivate my Socks5 box tomorrow to run a test again.
>
> > ---
> > Arno Garrels [TeamICS]
> > http://www.overbyte.be/eng/overbyte/teamics.html
>
>
>
> >> The SSL support should
> >> ideally be on top of proxy (socks or http proxy) support.
> >>
> >> - http proxy support is added in parallel to socks, and http
> >> processing is done after socks processing in the code. Only one
> >> type of proxy (socks or http) can be used in one socket. This
> >> design of course will not support proxy chaining. Ideally, proxy
> >> support should be flexible enough to chain any number of socks and
> >> http proxies that support CONNECT method.
> >>
> >> - the modification supports Basic authentication scheme only,
> >> and does not support Digest authentication scheme (quite some work
> >> :)
> >>
> >> - Once HTTP header is received, I'm reading one byte a time to read
> >> the rest of the reply, which is not the most efficient way. Since
> >> it's mostly reading from a buffer in memory, it should not be a big
> >> deal. This has no impact if HTTP proxy is not in use.
> >>
> >>
> >> --
> >> Best regards,
> >> Jack
> >>
> >> Saturday, December 9, 2006, 1:13:30 AM, you wrote:
> >>
> >>> Updated today.
> >>
> >>> --
> >>> Contribute to the SSL Effort. Visit
> >>> http://www.overbyte.be/eng/ssl.html
> >>> --
> >>> [EMAIL PROTECTED]
> >>> http://www.overbyte.be
> >>
> >>
> >>> ----- Original Message -----
> >>> From: "Francois PIETTE" <[EMAIL PROTECTED]>
> >>> To: <twsocket@elists.org>
> >>> Sent: Friday, December 08, 2006 8:27 PM
> >>> Subject: [twsocket] TWSocket support for HTTP proxy
> >>
> >>
> >>>> Jack has patched the latest beta (Downloaded about a week ago) to
> >>>> have TWSocket support http proxy tunneling. I've uploaded the file
> >>>> at http://www.overbyte.be/arch/dump/WSocketHttpProxy.zip for
> >>>> everyone review.
>
> --
> To unsubscribe or change your settings for TWSocket mailing list
> please goto http://www.elists.org/mailman/listinfo/twsocket
> Visit our website at http://www.overbyte.be
>
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
