3 ms·
Two CRLF pairs (one to terminate the status line, one to terminate the (empty) headers), which this is one CR short of. Trivially fixable, though it'd mess up t
by deathanatos 5y ago
Two CRLF pairs (one to terminate the status line, one to terminate the (empty) headers), which this is one CR short of. Trivially fixable, though it'd mess up the P slightly…
- jpegqs 5y agoThanks for noticing this, I fixed it on github. However, it seems that browsers are simply ignoring CRs. So that "\n\n" is enough.
- deathanatos 5y agoYeah, I would expect browsers to do a number of non-standard things. It is possible with most of them to construct & send malformed requests.