Thanks for the project. Been using it in my home lab for a little while now and experimenting with its use in my work environment where I have unfortunately found an issue. I have had a search here on GitHub and on Internet in general but haven't found anything similar.

When attempting to access Web GUI for one particular device 'brand', regardless using HTTP or HTTPS on the back end results in 'garbled' output.

Having a look at this made me think it was a character encoding mismatch. So I decided to capture the packets between the device and Warpgate (using HTTP to get 'clear text') and from the packet capture I can see the expected HTML.
In below example, 192.168.0.14 is my lab docker host and 192.168.0.118 is my lab device I am wanting to connect to (FortiGate firewall)

Looking in Docker logs there is no obvious errors or issues. You can see 200 returned for the page (which is presented as garble) and the favicon 404 (which is expected).

I haven't seen this problem in the handful of other systems I have configured before, and appears to be isolated the this brand so far, affecting 3 different that I have tested with. Other thought I had was the body is gziped and Warpgate not handling this correctly but I have other systems/servers that gzip encoded without issue (and given it is widely used), and the returned garble doesn't appear to be valid GZIP data.

I am unsure if there is anything obvious that I have missed here but I have looked at it over two different times/sessions and haven't picked up anything else. I have no experience in Rust, but basic programming and Docker knowledge. So any pointers help or guidance would be appreciated!