3 ms·

TLS is binary

• zimpenfish 10y ago
  But you can access the inner protocol by using `openssl s_client -connect host:port` as a TLS/SSL wrapper, can't you? (Edit: I realise you can likely also access/debug HTTP/2.0 streams with a CLI tool - I am currently ambivalent about text vs binary streams.)
  • Matthias247 10y ago
    Yes, you can also access/debug HTTP/2 content with curl or nghttp2. And the content of the request/response body streams is binary (in the sense that there is no predefined encoding) - just like in HTTP/1.1. That there is also a binary framing layer underneath should not care you from CLI user or application builders perspective. Just like you don't care in what number of IP frames your request was transmitted.
• Matthias247 10y ago
  as are Ethernet, IP, TCP, and everything else on the lower layers. I would say even say most networking protocols are binary. Some very high level protocols are not, but in my opinion working with binary ones in applications and libraries is much easier (no need to read an arbitrary amount of bytes and loop through all of them just to find a termination sequence, etc.)
• profmonocle 10y ago
  As are DNS, NTP, SSH, and DHCP. That's just off the top of my head.