4 ms·
Yes, several times. It was kept in because other text based protocols (like SMTP, HTTP) also specify the use of CRLF, at least for the request.
by spc476 6y ago
Yes, several times. It was kept in because other text based protocols (like SMTP, HTTP) also specify the use of CRLF, at least for the request.
- Aeolun 6y agoIt also doesn’t really hurt anyone, though it would be nice if new protocols could try to remove the need from their specs. We’re going to build new clients and servers anyway, so might as well handle just /n
- WoodenChair 6y ago> It also doesn’t really hurt anyone Well it does. Extra characters in the HTTP spec end up getting sent trillions of times per year over the Internet costing real money in bandwidth in aggregate.