This is probably caused by the fact that PageKite relies on the TLS
SNI extension to correctly route end-to-end HTTPS connections.
Quite a few APIs and libraries still do not do SNI correctly, which
means PageKite doesn't really know what to do with the incoming
request and will have to make an "educated guess". This can very
easily lead to the behavior you are seeing.
There are some workarounds; if you know you are connecting to a site
over PageKite, the most reliable way to make this work is to send an
HTTP CONNECT before you perform the SSL handshake.
- Bjarni
--
Bjarni R. Einarsson
Founder, lead developer of PageKite.
Make localhost servers visible to the world:
https://pagekite.net/