Indeed. Why not use nc and telnet on port 443 to test? Linux already has nc and Windows already has telnet.
You could of course use nc as the client too, but it would be an additional install on Windows. [0]
And nc wouldn't help if the firewall was stateful and actually expected to see HTTPS traffic on port 443, so I do see their logic of putting an actual webserver there.
But without sufficient detail, it does seem at first glance to be overkill ;-)
Bear in mind the server was at the Windows end, so no good with telnet over that side...
I wouldn't know how to do it in Golang because I don't use it. I would default to my most comfortable language, which is almost guaranteed to not be the most efficient method to do anything.
python -m SimpleHTTPServer 443Remember - the server end is Windows, and the guys at that end didn't know what to do if it wasn't an .msi or .exe.
Asked a programmer our side (.net) who said it'd take a couple of hours to write a simple webserver, package it up into an .msi and give it us. I got annoyed, did it in Golang in about 10 lines of code.
I then realised i'd compiled a Linux executable on Linux, remembered it did cross-compiling, 10 seconds later I had a Windows .exe. All for a simple webserver that printed "cock", not useful but it proved the tunnels worked.
Sometimes we overcomplicate the simplest shit.
EDIT: As it wasn't clear (my fault) - we were trying to get to port 443 at their end - they were on Windows, we mainly Linux but the guys I asked were .net programmers..