Closed lucasmichot closed 7 years ago
Can you explain the use-case (or the bug this prevents)? As far as I remember, this adapter is only used in unit testing...
It is, but tests are also run in Windows OS
Are you saying tests are not passing on Windows?
I am personally not using Windows for my development, but this has come an issue in other situations. I am curious to see if they pass on Widows tho
From a quick check, we only used assertContains
, never compared the full string.
Although this adapter is only used for testing, it seems to me that the most correct thing to do would be to use "\r\n" in all cases so that we're following the standard HTTP/1.1 message format?
We never resolved this one, right? Any objections to switching from \n
to \r\n
for the string adapter? (we can write some logic into the tests to auto-convert what we've typed – since all files are using unix LF EOLs).
(this would have the benefit of being technically valid for output in a HTTP response – though I would be surprised if anything actually rejected headers because of LF instead of CRLF).
Ensure line-break is not OS dependent.