summaryrefslogtreecommitdiffhomepage
path: root/src/event/quic/ngx_event_quic_protection.c
diff options
context:
space:
mode:
authorRoman Arutyunyan <arut@nginx.com>2025-05-20 15:33:20 +0400
committerRoman Arutyunyan <arut@nginx.com>2025-05-25 22:16:04 +0400
commitd76e3d301644cfc6a2d914976b6098eb98b9e5b9 (patch)
treeb3aa4ef70b07d641e9c5b6d0693bb121b389ba7d /src/event/quic/ngx_event_quic_protection.c
parent6a134dfd4888fc3850d22294687cfb3940994c69 (diff)
downloadnginx-tunnel.tar.gz
nginx-tunnel.tar.bz2
HTTP CONNECT proxy.tunnel
HTTP CONNECT method is now supported in HTTP/1 connections. It's disabled in all currently existing standard modules. A new variable $port is added that contains the port passed by client in HTTP CONNECT. The $host variable contains the host part. A new module ngx_http_tunnel module is added which establishes a tunnel to a backend. It supports the newly added HTTP CONNECT method and can be used to set up an HTTP CONNECT proxy. As recommended by RFC 9110, proxy target should be restricted to ensure safe proxying: : Proxies that support CONNECT SHOULD restrict its use to a limited set : of known ports or a configurable list of safe request targets. Example config: server { listen 8000; resolver dns.example.com; map $port $tun_port { 80 1; 443 1; } map $host $tun_host { hostnames; example.com 1; *.example.org 1; } map $tun_port$tun_host $tun { 11 $host:$port; } location / { tunnel_pass $tun; } } Request: $ curl -px 127.0.0.1:8000 http://example.com
Diffstat (limited to 'src/event/quic/ngx_event_quic_protection.c')
0 files changed, 0 insertions, 0 deletions