3 ms·
You would rarely implement HTTP/1.x yourself. You could, but there are dedicated libraries for that.
by dinomad 6y ago
You would rarely implement HTTP/1.x yourself. You could, but there are dedicated libraries for that.
- inopinatus 6y agoI still find myself connecting with a line-buffered client to GET / and so on, from time to time. Even in 2020 it's still the handiest way to diagnose some issues. I've always appreciated that most IETF protocols are text-oriented with line-buffered commands, and the option to speak the protocol directly in this fashion contributed enormously to my own understanding of SMTP, POP3, IMAP, IRC, NNTP, HTTP, FTP et al, and I always regretted not being to do the same with LDAP, SNMP, or BGP.
- dinomad 6y agoI can support the sentiment, but now when every public facing HTTP endpoint is TLS-protected... That ship has sailed. On internal networks HTTP/1 is not going anywhere any time soon, so there's that.
- inopinatus 6y agoFor TLS-wrapped protocols I'll use openssl s_client or ncat or some other simple stdin/out-friendly wrapper. There's no need to abandon line-oriented text-based application protocols just because the next layer down has a binary structure. After all, I'm not crafting TCP segments by hand. I recommend that internal network services use HTTPS, there's plenty of reason not to lower your standards internally.