If you're tunneling SSH through HTTP, shouldn't it actually be "Any protocol of top of web"?
Also interesting choice to use C++. I don't see the headers for Civet or Mongoose, or even libcurl in the Makefile. Is it your own HTTP implementation on both sides?
It doesn't really need to support the full HTTP spec given that both the client and server are under its control... Any subset will do; all you really need to do is respond with a 200 header.
I think I've used https://github.com/larsbrinkhoff/httptunnel (or another very similar tool) in the past to get around restrictive networks that pass http traffic. That was more than a decade ago though.
Currently Webrtc have to go thru TURN servers to achieve P2P calling on few networks,
Can a similar thing be used to send them over http/https and have a js code on receiving side, convert it into UDP Webrtc data, bypassing the need for a costly TURN server
Also interesting choice to use C++. I don't see the headers for Civet or Mongoose, or even libcurl in the Makefile. Is it your own HTTP implementation on both sides?