Free https proxy not supported error 512 software for linux

Phc is a program to validate free proxies for LAN users to reach the Internet by bypassing ISP proxies with strict limits. proxy hunter customed can be customized to change headers in test requests sent to free proxies, such as User_Agent.
You can also customize it with your own checksite, checksite port, or checksite key, switch between the CONNECT and GET method, etc., to test and filter free proxies.
It can be used to validate free socks5 proxies with a connect command or free HTTP proxies with a GET or CONNECT method. It can validate free proxies with a TCP tunnel.
The tunnel can be a free HTTP proxy, a free socks5 proxy, an HTTP proxy with basic authentication, or a socks5 proxy with username/password authentication.
Enhancements:
- Support for socks4 proxy(connect).
- Full command line options.
- The configuration file can also be appointed by command line options.
- Output file and input file with full path can be set by the user.

ftp.proxy is an application level gateway for FTP. It sits between a client and a server forwarding command and data streams supporting a subset of the file transfer protocol as described in RFC 959.
But, beside this basic function which makes the program useful on firewall or masqueraders it offers fixing the FTP server (e.g. for connections into a protected LAN) and proxy authentication.
Main features:
- ftp.proxy offers external access control programs (ACP), that is an external program decides if a user can use the proxy service or not. This decision can be made on username, host name, day of time etc.
- Since version 1.0.1 ftp.proxy supports also command control programs. Similar to ACPs the CCPs permit or deny access to certain FTP commands on the server, e.g. its possible to allow a user to get files but to deny any kind of uploads.

HAVP (HTTP Antivirus Proxy) is a proxy with a ClamAV anti-virus scanner. HTTP Anti Virus Proxy aims are continuous, non-blocking downloads and smooth scanning of dynamic and password protected HTTP traffic.
Havp antivirus proxy has a parent and transparent proxy mode. It can be used with squid or standalone.
Main features:
- HTTP Antivirus proxy
- Scans complete incomming traffic
- Nonblocking downloads
- Smooth scanning of dynamic and password protected traffic
- Can used with squid or other proxy
- Parent proxy support
- Transparent proxy support
- Logfile
- Process change to defined user and group
- Daemon
- Use Clamav (GPL antivirus)
- Operating System: Linux
- Written in C++
- Released under GPL
Enhancements:
- Experimental support was added for chunked Transfer-Encoding, which fixes some broken sites.
- The IGNOREVIRUS configuration directive was added for whitelisting virus names.
- The CLAMBLOCKBROKEN configuration directive was added.
- Detection with AVG was improved.
- HAVP is killed if database reloading fails for Library Scanner.
- The URL is logged when a crashed scanner process is detected.
- The build system updated, adding the --prefix, --sbindir, --sysconfdir, and --localstatedir options.

IMAP Proxy server is a caching IMAP proxy server. It was written to compensate for webmail clients that are unable to maintain persistent connections to an IMAP server. Most webmail clients need to log in to an IMAP server for nearly every single transaction.

This behaviour can cause tragic performance problems on the IMAP server. imapproxy tries to deal with this problem by leaving server connections open for a short time after a webmail client logs out.

When the webmail client connects again, imapproxy will determine if theres a cached connection available and reuse it if possible.

How does imapproxy keep track of which server connection is for which user?

Upon the first successful login to the real IMAP server (through the proxy), imapproxy fills in a little record that contains the username, an md5 digital signature of the password and the server socket descriptor thats being used.

After you log out and then log back in again, imapproxy just has to find a record that matches your username and password. These records are stored in a hash table (with the username being the hash key) in memory, so the lookups are pretty fast.

Can IMAP Proxy support multiple backend servers?

If you want IMAP Proxy to be able to proxy to multiple backend IMAP servers, you can run multiple instances of IMAP Proxy and make sure each instance is looking at a different configuration file.

Before you do this, take a look at perdition which appears to have been designed with this specific task in mind.

Spike Proxy is an open source HTTP proxy for finding security flaws in web sites.

SPIKE Proxy is part of the Spike Application Testing Suite and supports automated SQL injection detection, web site crawling, login form brute forcing, overflow detection, and directory traversal detection.

To Use:

python spkproxy.py [ optional port argument, 8080 is default ]
Then set up your browser to use that port for both HTTP and
HTTPS proxies.

Then watch the traffic go!

OpenSER is a collaborative project of its users, to develop a scalable and robust SIP server.
Anyone can contribute to one of next items:
- code development - OpenSER core, modules and adjacent applications
- documentation- writing or enriching documentation
- miscellaneous - different management tasks (e.g., web site maintenance)
- ideas - new ideas bring brilliant solutions
Main features:
- robust and performant SIP (RFC3261) Registrar server, Location server, Proxy server and Redirect server
- stateless and transactional statefull SIP Proxy processing
- support for UDP/TCP/TLS transport layers
- scripting language for configurations file. With a syntax similar to sripting languages, the configuration offers a powerful and flexible way to deploy custom SIP services.
- management interface via FIFO file and unix sockets
- pseudo-variables to access and manage parts of the SIP messages and attributes specific to users and server
- authentication, authorization and accounting (AAA) via database (MySQL, Postgress, text files), RADIUS and DIAMETER
- CPL - Call Processing Language (RFC3880)
- NAT traversal support for SIP and RTP traffic
- ENUM support
- load balancing and least cost routing extensions
- support for replication - REGISTER offer new functions for replicating client information (real source and received socket).
- logging capabilities - can log custom messages including any header or pseudo-variable and parts of SIP message structure.
- modular architecture - plug-and-play module interface to extend the servers functionality
Enhancements:
- This is the second patch release in 1.2.x series, including minor enhancements and bugfixes done since 1.2.1 was released.

Apache::ProxyConf is a Perl module that can generate proxy configuration for browsers.

SYNOPSIS

# In httpd.conf:

< Location / >
SetHandler perl-script
PerlHandler Apache::ProxyConf
PerlSetVar ProxyConfConfig "/some/location/proxyconf.ini"
< /Location >

The Apache::ProxyConf is used to configure the proxy settings in browsers automatically. The modules returns a script that conforms to the Navigator Proxy Auto-Config File Format. The module is suitable for large scale installations that have multiple (cascading) proxies. It can be used to return the closest proxy based on the network topology. Failover and load distribution is also provided.

Browser configuration

The (virtual) webserver must be entered in the Autoconfigure URL of the browser to make use of the ProxyConf script.

http://proxyconf.some.domain/

In IE the URL must be specified in the Address field, just below the Use automatic configuration script tickbox.

THE CONFIGURATION FILE

The ProxyConf module first reads a .ini-style configuration file to determine the proxy settings of the network. The configuration file contains three sections: proxy, noproxy and https.

The proxy section

The sections proxy and https have an identical format. They contain lines of the form subnet=proxyip:port.

Single proxy

[proxy]
172.16.32.0/20=172.16.32.10:3128

The subnet 172.16.32.0/20 has a single proxy defined. The proxy server is 172.16.32.10 and it listens on port 3128.

Multiple proxies

[proxy]
172.16.0.0/20=172.16.0.10:3128,172.16.0.20:3128

Multiple proxy servers are defined in a comma separated list. In this example clients in the 172.16.0.0/20 subnet use 172.16.0.10 as their primary proxy server. When this server becomes unavailable, the clients will move over to 172.16.0.20 for their proxy requests.

Multiple proxies with load distribution

[proxy]
172.16.0.0/20=(172.16.0.10:3128,172.16.0.20:3128)

When proxy servers are placed between brackets, the load is distribution amongst the proxies. Some clients will have the first proxy as primary and some clients will have the second proxy as primary. The other proxy is used as a backup. The order in which the proxies are tried depends on the IP address of the client. The script is deterministic, so for a given IP address the priority list is always the same.

To determine the proxy list for a given IP address multiple rules may be applied. Subnets are tried from the highest to the lowest mask. The module puts all proxies that are found in a list.

The noproxy section

The noproxy section contains hosts that should be contacted by the clients directly. Noticeably, web servers that use NTLM authentication will not work when clients connect to them via a proxy server. The syntax for specifying noproxy hosts is subnet=fqhn1,fqhn2,... Alternatively, the multiline syntax can be used, as shown in this example.

[noproxy]
0.0.0.0/0=<<less