Introduction
What’s New in Version 2
Changelog
Proxifier Migration Notes
Quick Start
Proxy Server Settings
Proxification Rules
Profiles
User Interface
Name Resolution
Proxy Chains
HTTP Proxy Support
Direct Connections
Log Files
System and Other Users' Connections
Connection Loop Detection
Network Error Codes
Order Proxifier
Trial Version
Technical Support
End-User License Agreement
Related Help Topics |
---|
(This topic is about HTTP proxy servers. Please do not confuse this with HTTPS).
It is a common misconception to confuse HTTP proxy and HTTPS proxy. HTTP proxy servers can process HTTP connections (port 80). They can also support HTTPS connections (SSL) but usually such connections are only allowed on port 443 (the standard port for HTTPS). For example this is the default configuration for Squid and Microsoft ISA proxy servers. If an HTTP proxy allows HTTPS connections on arbitrary ports, it can be called HTTPS proxy server (also called CONNECT or SSL proxy). In this case it can be used for generic TCP connections like SOCKS v4/5 proxy.
Proxifier can work with HTTP proxy servers that do not support HTTPS on arbitrary ports. Due to the technical limitation of this protocol it is only possible to process HTTP connections with such proxy servers. This means that you must configure the Proxification Rules accordingly.
You can enable HTTP proxy support at HTTP Proxy tab at Profile->Advanced window.
After that you will be able to add HTTP proxy server just like any other type of proxies. Once HTTP proxy server is added, make sure that you properly set the Proxification Rules. If you want to process HTTPS connections through this proxy also, you should add this proxy separately as HTTPS.
Suppose proxy.example.net:8080 is a usual HTTP proxy and supports HTTP on port 80 and HTTPS on port 443 and we want to configure Proxifier to process HTTP/HTTPS connections (web browsing) through it.
The following images illustrate the correct setup.
Proxy Settings: