We use HSTS now, which dictates that every page must be served over SSL.
Sometimes, and especially on mobile networks, the SSL handshake may be interrupted by bad signal. In that moment the browser has nothing... so the only thing it can do is to tell you this and let you retry.
Likely to be caused by using a mousedown / mouseup / touchend etc event on mobile to speed things up? The basic 'click' event on a phone introduces delay as it tries to disambiguate a genuine click from a scroll event. That delay might be exactly what you do want in this instance.
We use HSTS now, which dictates that every page must be served over SSL.
Sometimes, and especially on mobile networks, the SSL handshake may be interrupted by bad signal. In that moment the browser has nothing... so the only thing it can do is to tell you this and let you retry.