Apache > HTTP Server > Documentation > Version 2.4 > Modules

Apache Module mod_proxy_connect

Available Languages:  en  |  fr  |  ja 

Description:mod_proxy extension for CONNECT request handling
Module Identifier:proxy_connect_module
Source File:mod_proxy_connect.c


This module requires the service of mod_proxy. It provides support for the CONNECT HTTP method. This method is mainly used to tunnel SSL requests through proxy servers.

Thus, in order to get the ability of handling CONNECT requests, mod_proxy and mod_proxy_connect have to be present in the server.

CONNECT is also used when the server needs to send an HTTPS request through a forward proxy. In this case the server acts as a CONNECT client. This functionality is part of mod_proxy and mod_proxy_connect is not needed in this case.


Do not enable proxying until you have secured your server. Open proxy servers are dangerous both to your network and to the Internet at large.

Support Apache!



Bugfix checklist

See also


Request notes

mod_proxy_connect creates the following request notes for logging using the %{VARNAME}n format in LogFormat or ErrorLogFormat:

The local port used for the connection to the backend server.

AllowCONNECT Directive

Description:Ports that are allowed to CONNECT through the proxy
Syntax:AllowCONNECT port[-port] [port[-port]] ...
Default:AllowCONNECT 443 563
Context:server config, virtual host
Compatibility:Moved from mod_proxy in Apache 2.3.5. Port ranges available since Apache 2.3.7.

The AllowCONNECT directive specifies a list of port numbers or ranges to which the proxy CONNECT method may connect. Today's browsers use this method when a https connection is requested and proxy tunneling over HTTP is in effect.

By default, only the default https port (443) and the default snews port (563) are enabled. Use the AllowCONNECT directive to override this default and allow connections to the listed ports only.

Available Languages:  en  |  fr  |  ja 



This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our mailing lists.