HTTP Gateway examples?

First of all.....Happy New Year to you!  I hope you have a successful and
joyous new year.

As for the HTTP Gateway examples....  I'm looking for some sample code that
may illustrate techniques useful in coding an HTTP Gateway.

I want to be able to connect 2 PCs (both behind firewalls) via an HTTP
connection.  FTP is also acceptable for this project, but HTTP is best.

Have you seen any code or articles that would be helpful in this respect?

Thank you for your time.

Jim Hubbard

Jim Hubbard wrote:
> First of all.....Happy New Year to you!  I hope you have a successful
> and joyous new year.
>
> As for the HTTP Gateway examples....  I'm looking for some sample
> code that may illustrate techniques useful in coding an HTTP Gateway.

What is a HTTP gateway? Gateways are ISO layer 3 devices, way below HTTP's
location in the standard network stack.

> I want to be able to connect 2 PCs (both behind firewalls) via an HTTP
> connection.  FTP is also acceptable for this project, but HTTP is
> best.

Regardless of whether you run HTTP or FTP, if the communication is supposed
to be bidirectional, you'll need to run both server and client software on
both boxes. Since there's no native FTP support in .NET before version 2.0,
using HTTP is probably easier to implement (System.Net.WebClient or
System.NetWebRequest) and certainly a lot more firewall friendly -- I assume
port 80 is open on both firewalls.

Cheers,

--
Joerg Jooss
www.joergjooss.de
news@joergjooss.de

Jim,

This is stuff I am absolute not interested in at the moment, however
searching for the right page for somebody else I saw this.

http://msdn.microsoft.com/msdnmag/i...es/default.aspx

Maybe you can need it (although it is aspnet and I doubt it, however
something is in my opinion always better than nothing)

Cor
"Jim Hubbard" <reply@groups.please>

> First of all.....Happy New Year to you!  I hope you have a successful and
> joyous new year.
>
> As for the HTTP Gateway examples....  I'm looking for some sample code
> that may illustrate techniques useful in coding an HTTP Gateway.
>
> I want to be able to connect 2 PCs (both behind firewalls) via an HTTP
> connection.  FTP is also acceptable for this project, but HTTP is best.
>
> Have you seen any code or articles that would be helpful in this respect?
>
> Thank you for your time.
>
> Jim Hubbard
>
>

If you mean HTTP Server app , look at Webster example on
http://www.microsoft.com/msj/archive/S25F.aspx

Arkady

"Jim Hubbard" <reply@groups.please> wrote in message
news:ou6dnX6GL5VpZ0vcRVn-hg@giganews.com...
> First of all.....Happy New Year to you!  I hope you have a successful and
> joyous new year.
>
> As for the HTTP Gateway examples....  I'm looking for some sample code
that
> may illustrate techniques useful in coding an HTTP Gateway.
>
> I want to be able to connect 2 PCs (both behind firewalls) via an HTTP
> connection.  FTP is also acceptable for this project, but HTTP is best.
>
> Have you seen any code or articles that would be helpful in this respect?
>
> Thank you for your time.
>
> Jim Hubbard
>
>

You are right....I should have called it an HTTP-Tunnel to be more precise.


"Joerg Jooss" <joerg.jooss@gmx.net> wrote in message
news:e5yoz0K8EHA.2788@TK2MSFTNGP15.phx.gbl...
> Jim Hubbard wrote: 
>
> What is a HTTP gateway? Gateways are ISO layer 3 devices, way below HTTP's
> location in the standard network stack.
> 
>
> Regardless of whether you run HTTP or FTP, if the communication is
> supposed to be bidirectional, you'll need to run both server and client
> software on both boxes. Since there's no native FTP support in .NET before
> version 2.0, using HTTP is probably easier to implement
> (System.Net.WebClient or System.NetWebRequest) and certainly a lot more
> firewall friendly -- I assume port 80 is open on both firewalls.
>
> Cheers,
>
> --
> Joerg Jooss
> www.joergjooss.de
> news@joergjooss.de
>

Jim Hubbard wrote:
> You are right....I should have called it an HTTP-Tunnel to be more
> precise.

So at the end of the day, it's a normal HTTP connection used to transport
Yet Another Protocol. This changes little -- you still need a web server and
a web client ;-)

Cheers,

--
Joerg Jooss
www.joergjooss.de
news@joergjooss.de

I want to duplicate the activeX component found at
http://www.http-tunnel.com/html/sol...nel/activex.asp in .Net
and the associated HTTP-Tunnel Server (also found on the same site).

It would be used to get around firewalls for a remote help solution to be
provided freely to my customers.

Thanks for sticking with me......

Jim Hubbard


"Joerg Jooss" <joerg.jooss@gmx.net> wrote in message
news:OZuKjjv8EHA.4028@TK2MSFTNGP15.phx.gbl...
> Jim Hubbard wrote: 
>
> So at the end of the day, it's a normal HTTP connection used to transport
> Yet Another Protocol. This changes little -- you still need a web server
> and a web client ;-)
>
> Cheers,
>
> --
> Joerg Jooss
> www.joergjooss.de
> news@joergjooss.de
>

Jim Hubbard wrote:
> I want to duplicate the activeX component found at
> http://www.http-tunnel.com/html/sol...nel/activex.asp in
> .Net and the associated HTTP-Tunnel Server (also found on the same
> site).
> It would be used to get around firewalls for a remote help solution
> to be provided freely to my customers.

Note that "getting around the firewall" is highly misleading. You
(hopefully) don't get around the firewall, you just sneak your stuff through
port 80, which is usually open to allow for HTTP traffic.

If you want to implement a true general HTTP tunneling solution, you
probably want to use a more powerful network API than what .NET currently
offers, like Indy (http://www.indyproject.org/). And if you need to hook
into WinSock like HTTP Tunnel does, I guess you need to deal with unmanaged
code anyway.

Cheers,

--
Joerg Jooss
www.joergjooss.de
news@joergjooss.de