Skip to content

Commit 5b0d95b

Browse files
committed
add more wiki references and add docker compose recipe
1 parent de1cd59 commit 5b0d95b

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

README.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -131,6 +131,22 @@ stream
131131
}
132132
```
133133

134+
### Example: HTTP proxy over TLS (ACME-issued cert) behind Traefik reverse proxy running in Docker Compose and performing SNI routing
135+
136+
Have following labels attached to dumbproxy service in compose file:
137+
138+
```yaml
139+
traefik.enable: "true"
140+
traefik.tcp.routers.dumbproxy.service: dumbproxy
141+
traefik.tcp.routers.dumbproxy.rule: HostSNI(`<your-domain>`)
142+
traefik.tcp.routers.dumbproxy.tls: "true"
143+
traefik.tcp.routers.dumbproxy.tls.passthrough: "false"
144+
traefik.tcp.services.dumbproxy.loadBalancer.server.port: 8080
145+
traefik.tcp.services.dumbproxy.loadbalancer.proxyProtocol.version: 2
146+
```
147+
148+
dumbproxy service should be run in plaintext mode as TLS is handled on Traefik side. So options would be just `-bind-address=:8080 -proxyproto` and probably something for authorization. This recipe is explained in [Wiki](https://github.com/SenseUnit/dumbproxy/wiki/Docker-Compose-Deployment-behind-Traefik-Reverse-Proxy) with more details and configuration files provided for context.
149+
134150
### Example: HTTP proxy over TLS (BuyPass automatic certs)
135151

136152
Run HTTPS proxy (HTTP proxy over TLS) with automatic certs from BuyPass on port 443 with `Basic` authentication with username `admin` and password `123456`:
@@ -145,6 +161,8 @@ dumbproxy \
145161
-autocert-http :80
146162
```
147163

164+
See [Wiki](https://github.com/SenseUnit/dumbproxy/wiki) for more examples, recipes and notes.
165+
148166
## Using HTTP-over-TLS proxy
149167

150168
It's quite trivial to set up program which supports proxies to use dumbproxy in plain HTTP mode. However, using HTTP proxy over TLS connection with browsers is little bit tricky. Note that TLS must be enabled (`-cert` and `-key` options or `-autocert` option) for this to work.

0 commit comments

Comments
 (0)