ComponentSpace Professional .NET and ActiveX components for developers
ComponentSpace Home | Products | Downloads | Support | Purchase | Services | About Us
 
SOCKS and HTTP Proxy for your C#, VB.NET, and ASP.NET applications

SOCKS and HTTP Proxy for your C#, VB.NET, and ASP.NET applications

Product Links
 Purchase
single developer - $99 
4 developer team - $199 
8 developer team - $299 
site license - $399 
site + source - $799 
 
 Download
 Documentation
 Code Samples
 Screen Shots
 Testimonials
 Ask a Question

Send messages from behind the corporate firewall via an HTTP or SOCKS proxy server.

The Proxy component for .NET is a fully featured, easy to use implementation of the HTTP and SOCKS proxy protocols for .NET and ASP.NET applications. It acts as a proxy client and supports outbound TCP connections to HTTP, SOCKS v4, SOCKS v4A and SOCKS v5 proxy servers. The component offers .NET developers an easy way to traverse firewalls, using proxy servers, from within their applications.

Part of the award winning .NET Internet Component Suite, the component is designed specifically for .NET and is written in 100% managed C# code.


What's Included


HTTP Proxy Client

  • Connects to an HTTP proxy server using HTTP CONNECT (tunneling)

  • Returns a TcpClient object for communications with the server

  • No restrictions on the data transferred (HTTP, FTP, etc.)

  • Connect either synchronously or asynchronously


SOCKS Proxy Client

  • Connects to a SOCKS v4, SOCKS v4A or SOCKS v5 proxy server

  • Returns a TcpClient object for communications with the server

  • No restrictions on the data transferred (HTTP, FTP, etc.)

  • Connect either synchronously or asynchronously


ProxyClientFactory and IProxyClient

  • IProxyClient interfaces permits interaction in a proxy protocol neutral manner

  • ProxyClientFactory creates a proxy client of the specified type implementing IProxyClient


Designed for .NET

  • Object oriented design specifically for the .NET framework

  • 100% managed code written in C#

  • Make either synchronous or asynchronous (Begin/End) calls

  • Asynchronous calls may either use events or callbacks