Open Marenz opened 7 years ago
Sorry for the late reply, I just noticed this now. The call trace above looks like the connection is actually just an unencrypted HTTP connection, just the Libevent2TCPConnection
wrapped in a LimitedInputStream
. However, the setup sequence looks unsuspicious. Is there any chance that the code below does not belong to the setup sequence below?
This is some time ago now. But I suspect what happened was that I called the https connection with a http:// prefix in the browser (happens easily when you use non-std ports).
Maybe it would be good to have some dumb check in the HTTPS part to see if it is normal HTTP and give a better error message?
Very suddenly, my HTTPS connections start to fail. I was using the dummy certificate at first provided in the https example, but I also generated my own for another instance, but both show the same problem. One is vibe 29, the other the latest.
Here is what the log shows:
Here is the code that sets up the HTTPS: