Garbled output - possible character encoding issue about warpgate HOT 4 OPEN

Could you try downloading the response body as-is (browser devtools -> reload page -> network tab -> find the document request (first) -> copy as curl -> run it and save into file) and feed it to file to see if it gets recognized as some other compression format maybe?

Also please compare the headers returned through Warpgate and when accessing the page directly

from warpgate.

I'm remote from my lab today but I have been able to gather some information.

I've attempted a few different file typing/identifying methods to see if it is 'compressed' or another file type, but everything is returning it a generic binary data, so I don't believe it is a mistyped file/return.

Comparing the headers at the browser you can see that there is a difference in the content-type. Warpgate returns text/html; charset=utf-8 whereas a NGINX reverse proxy I have set up only returns text/html;. Interestingly, this appears to be added by Warpgate as when capturing the same connection attempt behind Warpgate, the response from the device/server does not contain the utf-8 charset.

NGINX browser headers

Warpgate browser headers

Response from device

Of course this doesn't make too much sense why this would be causing some issues, because the webpage itself includes the meta charset of utf-8 unless there is some weird browser or Warpgate interaction (stepping well out of my comfort zone here). But that said, I have this issue on Windows and Mac under Firefox and Chrome (this testing/output from Windows Firefox). I can't recall if I have tested under MacOS Safari but I can confirm same behavior on IOS Safari.

from warpgate.

Is there a chance you could run tcpdump on the server side to capture the traffic directly between Warpgate and Fortigate?

from warpgate.

The "Response from device" above is a packet capture (loaded into wireshark) captured on the FortiGate, is that sufficient? I came provide that.

I could try and capture on my Docker host but would be trickier as Docker and FortiGate are both VMs on the same physical host, and presumably show the same being direct without anything between them.

from warpgate.