https://github.com/rpardini/nginx-proxy-connect-stable-alpine

nginx:stable-alpine + proxy_connect (multiarch image)
https://github.com/rpardini/nginx-proxy-connect-stable-alpine

connect-proxy docker multiarch nginx

Last synced: 3 months ago
JSON representation

nginx:stable-alpine + proxy_connect (multiarch image)

• Host: GitHub
• URL: https://github.com/rpardini/nginx-proxy-connect-stable-alpine
• Owner: rpardini
• Created: 2018-06-27T22:15:23.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2021-07-11T18:12:47.000Z (over 3 years ago)
• Last Synced: 2024-04-20T19:20:44.020Z (10 months ago)
• Topics: connect-proxy, docker, multiarch, nginx
• Language: Dockerfile
• Homepage:
• Size: 160 KB
• Stars: 9
• Watchers: 2
• Forks: 14
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# nginx:stable-alpine + proxy_connect

Upstreams: 

- [nginx:stable-alpine](https://github.com/nginxinc/docker-nginx/tree/master/stable/alpine) (due this has since long diverged)

- [ngx_http_proxy_connect_module](https://github.com/chobits/ngx_http_proxy_connect_module)

I removed gpg sig verification for the sake of faster builds.

Also most modules with external dependencies were removed.

# master (`:latest`) is actually unstable

For stable versions, use the tagged builds, eg, `nginx-1.18.0-alpine-3.12.1`

## Usage

It's on [Docker Hub](https://hub.docker.com/r/rpardini/nginx-proxy-connect-stable-alpine/); `:latest` is from master and unstable.

```bash 

docker run -it -p 8081:80 rpardini/nginx-proxy-connect-stable-alpine

```

- Just like `nginx:stable-alpine`, but you can use `proxy_connect;`.

- Also `proxy_connect_address $someVar;` is supported; this has the "rewrite" version of the patch

- you can map on `$connect_host`

- log `$connect_addr` for host:port of the final destination

## Why?

I wanted a more contained way of doing DNS overrides.

If you can convince a client program to use an https proxy, and inject your own CA certificate as trusted, 

you can use `proxy_connect` to send traffic to a second nginx server and do caching, filtering, rewriting, 

and who knows what else there.