nsnshsuejeb
Re:CRLF is obsolete and should be abolished
on Sunday October 13, 2024 @05:51PM (#41831994)
No need. Just convince the king (e.g. Google for HTTP) to make a tweak in the next standard version.
Re:CRLF is obsolete and should be abolished
on Sunday October 13, 2024 @05:49PM (#41831972)
Not defending the producer, just making pragmatic choices!
Re:CRLF is obsolete and should be abolished
on Sunday October 13, 2024 @05:46PM (#41831938)
The letters after the dot in my filename don't map 1 to 1 with the file format.
Re:CRLF is obsolete and should be abolished
on Sunday October 13, 2024 @05:42PM (#41831898)
Yes. We all know how to do this. You know that API version thingy. I agree to drop the carriage return when not needed but do it in future protocols.
Obviously IPv6 shows you need to be patient. Your great grandkids may see a useless carriage return!
Windows doesn't help here.
Re:CRLF is obsolete and should be abolished
on Sunday October 13, 2024 @05:39PM (#41831874)
Elephant in the room is the trillions of actual servers and user agents that would need to be tested and patched if you retroactively change a standard. Luckily there are some digits after HTTP that allow the concept of new versions of the standard.