connect proxy tunnel 1.1 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News connect proxy tunnel 1.1 (Default branch)
# 1  
Old 03-04-2008
connect proxy tunnel 1.1 (Default branch)

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 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. License: MIT/X Consortium License Changes:
cpt was not able to drop privileges, because of incorrect order in setgid/setuid.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. Web Development

Http connect to proxy to websockets

I am having a hard time with this one. We have a websocket server listening on port 80 at myserver.com/wsDemo?ID=12. We need to test a client program by connecting it to this server through a proxy. I am trying nginx 1.2.7 as the proxy on port 8080, running on proxy-server. We want the client to... (1 Reply)
Discussion started by: glev2005
1 Replies

2. IP Networking

Blocking HTTP tunnel in squid proxy 2.5

Does any one know how to block HTTP Tunnel in squid proxy server. Pls reply (1 Reply)
Discussion started by: vishwanathhcl
1 Replies
Login or Register to Ask a Question
CURLOPT_PROXY_CAINFO(3) 				     curl_easy_setopt options					   CURLOPT_PROXY_CAINFO(3)

NAME
CURLOPT_PROXY_CAINFO - path to proxy Certificate Authority (CA) bundle SYNOPSIS
#include <curl/curl.h> CURLcode curl_easy_setopt(CURL *handle, CURLOPT_PROXY_CAINFO, char *path); DESCRIPTION
This option is for connecting to a HTTPS proxy, not a HTTPS server. Pass a char * to a zero terminated string naming a file holding one or more certificates to verify the HTTPS proxy with. If CURLOPT_PROXY_SSL_VERIFYPEER(3) is zero and you avoid verifying the server's certificate, CURLOPT_PROXY_CAINFO(3) need not even indicate an accessible file. This option is by default set to the system path where libcurl's cacert bundle is assumed to be stored, as established at build time. If curl is built against the NSS SSL library, the NSS PEM PKCS#11 module (libnsspem.so) needs to be available for this option to work prop- erly. (iOS and macOS only) If curl is built against Secure Transport, then this option is supported for backward compatibility with other SSL engines, but it should not be set. If the option is not set, then curl will use the certificates in the system and user Keychain to verify the peer, which is the preferred method of verifying the peer's certificate chain. The application does not have to keep the string around after setting this option. DEFAULT
Built-in system specific PROTOCOLS
Used with HTTPS proxy EXAMPLE
TODO AVAILABILITY
Added in 7.52.0 For TLS backends that don't support certificate files, the CURLOPT_PROXY_CAINFO(3) option is ignored. Refer to https://curl.haxx.se/docs/ssl-compared.html RETURN VALUE
Returns CURLE_OK if the option is supported, CURLE_UNKNOWN_OPTION if not, or CURLE_OUT_OF_MEMORY if there was insufficient heap space. SEE ALSO
CURLOPT_PROXY_CAPATH(3), CURLOPT_PROXY_SSL_VERIFYPEER(3), CURLOPT_PROXY_SSL_VERIFYHOST(3), CURLOPT_CAPATH(3), CURLOPT_SSL_VERIFYPEER(3), CURLOPT_SSL_VERIFYHOST(3), libcurl 7.54.0 December 21, 2016 CURLOPT_PROXY_CAINFO(3)