cpt (connect proxy tunnel) aims to be running in front of any HTTPS server. It forwards all requests that don't call for a "CONNECT .." to the normal HTTPS server. There is no error handling for mistaken requests; they go straight to the default server.
A request that doesn't pass the conditions is passed forward too, and the Web server will handle it (with the default error page). Users should be unaware that cpt is running as a proxy.
Apache has a module "mod_proxy" that allows you to open a connecttion through the webserver to another port. (Dag Wieers has a good HOWTO for Apache and proxytunnel: http://dag.wieers.com/howto/ssh-http-tunneling/)
Other Webserver like lighttpd, nginx, .. don't have such an impementation. I wrote cpt to add this feature.
cpt aims to be running in front of any https server. It forwards all requests that don't call for a "CONNECT .." to the normal https server. There is no error handling for misbuild requests. They go straight forward to the default server. A request that doesn't pass the conditions is passed forward too, the webserver will handle it (with the default error page). There will be no awareness that cpt is running as proxy.
cpt is build to be secure, but you can disable all checks, which is a security leak and therefore not! recommended. Configuration is done by editing "cpt_conf.h" - see there for more information. So there is (hopefully) no way to manipulate the binary file and change any restriction. There is a little disadvantage by this.. you have to compile cpt every time by yourself. There will be no binary, because there is no sense in having a standard option set.
Product's homepage
What's New in This Release: [ read full changelog ]
· This release adds code cleanups and minor bugfixes for misbuild requests, and integration of the stunnel configuration sample and startup with stunnel.
Find us on Google+
