RE: Re: [squid-users] Microsft WCF net.tcp connections Squidable?

>"net.tcp" appears to be what the rest of the world call TCP sockets.
>So no a socket descriptor cannot be transmitted over HTTP.

Ok, thanks. In research, I'm reading about people compiling Squid with SOCKS5 support ... would that enable socket-proxying within Squid? Or is there some creative way to generalize/leverage the FTP proxying support (since the control channel on an FTP session is a TCP socket, no?)?

If not ... may have to move to ssh tunnels or stunnel or something, for at least these connections -- and there are real disadvantages relative to Squid with doing that. Nuts.

-----Original Message-----
From: Amos Jeffries [mailto:squid3_at_treenet.co.nz]
Sent: Wednesday, August 18, 2010 8:30 PM
To: squid-users_at_squid-cache.org
Subject: EXTERNAL: Re: [squid-users] Microsft WCF net.tcp connections Squidable?

On Wed, 18 Aug 2010 16:50:33 -0400, "Bucci, David G"
<david.g.bucci_at_lmco.com> wrote:
> I've been googling, but can't find any clear indication ... does
> anyone know of the "net.tcp" construct, in the Windows Communication
Foundations
> or whatever-the-heck-it's-called, can be proxied through squid?

"net.tcp" appears to be what the rest of the world call TCP sockets. So no a socket descriptor cannot be transmitted over HTTP.
The SOAP/JASON/AJAX/todays-fad requests sent down it apparently has meta headers formatted as full extensible XML files instead of simple Mime "Foo:
data".

Amos
Received on Thu Aug 19 2010 - 16:15:08 MDT