Not true anymore. https are getting blocked too. Last few lines of `curl --trace - https://thepiratebay.org/` https://thepiratebay.org/` on Jio ISP. Full log h

Not true anymore. https are getting blocked too. Last few lines of `curl --trace - https://thepiratebay.org/` https://thepiratebay.org/` on Jio ISP. Full log https://gist.github.com/anonymous/27ddfa674233d8d17a007f1b3fc1106e https://gist.github.com/anonymous/27ddfa674233d8d17a007f1b3f... => Send SSL data, 5 bytes (0x5) 0000: 15 03 03 00 1a ..... == Info: TLSv1.2 (OUT), TLS alert, Server hello (2): => Send SSL data, 2 bytes (0x2) 0000: 02 46 .F == Info: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number == Info: Closing connection 0 So TLS handshake is being interrupted. If you think about it, https blocking is actually more efficient. curl log does not show the last fake rcvd packet. Anyone know how to do that ?