You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+15-5Lines changed: 15 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,7 @@ Table of Contents
15
15
*[example for curl (CONNECT request in https)](#example-for-curl-connect-request-in-https)
16
16
*[example for browser](#example-for-browser)
17
17
*[example for basic authentication](#example-for-basic-authentication)
18
+
*[example for proxying WebSocket](#example-for-proxying-websocket)
18
19
*[Install](#install)
19
20
*[select patch](#select-patch)
20
21
*[build nginx](#build-nginx)
@@ -327,6 +328,13 @@ We can do access control on CONNECT request using nginx auth basic module.
327
328
See [this guide](https://github.com/chobits/ngx_http_proxy_connect_module/issues/42#issuecomment-502985437) for more details.
328
329
329
330
331
+
Example for proxying WebSocket
332
+
------------------------------
333
+
334
+
* Note that nginx has its own WebSocket reverse proxy module, which is is not limited to the CONNECT tunnel, see [nginx.org doc: Nginx WebSocket proxying](https://nginx.org/en/docs/http/websocket.html) and [nginx.com blog: NGINX as a WebSocket Proxy](https://www.nginx.com/blog/websocket-nginx/).
335
+
* This module enables the WebSocket protocol to work over the CONNECT tunnel, see https://github.com/chobits/ngx_http_proxy_connect_module/issues/267#issuecomment-1575449174
0 commit comments