Changes between Initial Version and Version 1 of Ticket #19251, comment 4
- Timestamp:
- Nov 16, 2012, 4:49:13 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #19251, comment 4
initial v1 1 1 Replying to [comment:3 claudep]: 2 2 > If browsers would systematically return CRLF, you would be right. But this isn't always true, so the situation is already inconsistent and somewhat broken. 3 3 4 4 I didn't explain it well, but my reasoning was: 5 - regular requests always use CRLF: if we normalize to CRLF ,we're backwards compatible, if we normalize to LF, we aren't.5 - regular requests always use CRLF: if we normalize to CRLF; we're backwards compatible, if we normalize to LF, we aren't. 6 6 - AJAX requests are browser dependent: no matter which way we normalize, it will have side effects for some people. 7 7 8 Although LF is the preferred line ending on Linux and Unix, it isn't "better" or "more correct". For instance HTTP and SMTP use CRLF everywhere. 9 8 10 In my opinion this is a basic browser interoperability issue that is better left to browser developers / W3C / etc.; but if you're keen on fixing it in Django that's just fine.