I have a reverse proxy setup to connect to my Duet from remote and it works flawlessly with DWC 2RC7. I remember there being an issue with reverse proxy in earlier release candidates and I don't remember which one actually fixed it but it works now.
Though I have to say I only use HTTP (encryption is implemented over an SSH tunnel) and a subdomain in my specific setup:
server {
listen 80;
server_name duet.localhost;
# Some upgrades here to be (able to be) more efficient
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
# Tell upstream where this request is coming from
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Host $http_host;
location / {
proxy_pass http://192.168.178.22;
proxy_set_header Host $http_host;
# Don't limit upload size and pass it on immediately without buffering
client_max_body_size 0;
proxy_request_buffering off;
}
}
EDIT: Regarding HTTPS I just create a Pull Request that replaces the hard-coded http: by location.protocol as mentioned by @Jacotheron.
