mirrors/caddy-website
1
0
Fork 0
mirror of https://github.com/caddyserver/website.git synced 2025-04-22 04:56:17 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

matchers: Update websockets examples

Browse source 
To distinguish HTTP/1.1 and HTTP/2
This commit is contained in:
Matthew Holt 2025-02-04 15:21:07 -07:00
parent f0a4b9516a
commit 8349a0e227
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
src/docs/markdown/caddyfile/matchers.md
View file

@ -146,7 +146,7 @@ Then you can use the matcher like so, by specifying it as the first argument to
directive @name directive @name
``` ```
For example, this proxies websocket requests to `localhost:6001`, and other requests to `localhost:8080`. It matches requests that have a header field named `Connection` _containing_ `Upgrade`, **and** another field named `Upgrade` with exactly `websocket`: For example, this proxies HTTP/1.1 websocket requests to `localhost:6001`, and other requests to `localhost:8080`. It matches requests that have a header field named `Connection` _containing_ `Upgrade`, **and** another field named `Upgrade` with exactly `websocket`:
```caddy ```caddy
example.com { example.com {
@ -441,10 +441,10 @@ Match requests that do not have the `Foo` header field at all:
@not_foo header !Foo @not_foo header !Foo
``` ```
Using an [CEL expression](#expression), match WebSocket requests by checking for the `Connection` header containing `Upgrade` and the `Upgrade` header equalling `websocket`: Using an [CEL expression](#expression), match WebSocket requests by checking for the `Connection` header containing `Upgrade` and the `Upgrade` header equalling `websocket` (HTTP/2 has the `:protocol` header for this):
```caddy-d ```caddy-d
@websockets `header({'Connection':'*Upgrade*','Upgrade':'websocket'})` @websockets `header({'Connection':'*Upgrade*','Upgrade':'websocket'}) || header({':protocol': 'websocket'})`
``` ```