Re: [whatwg/fetch] Acting on incomplete headers (#472)

https://wpt.fyi/results/fetch/h1-parsing/status-code.window.html also confirms this as my test code was rather sloppy:
```python
def main(request, response):
    output = b"HTTP/1.1 "
    output += request.GET.first(b"input")
    output += b"\nheader-parsing: is sad\n"
    response.writer.write(output)
    response.close_connection = True
```
All browsers were able to find the header `header-parsing` in the response, despite the lack of two newlines after it (let's ignore CRLF vs lone LFs here).

@whatwg/security @whatwg/http is this something we think could be fixed or should we enshrine this as a HTTP/1 parsing quirk in #1156?

(@njsmith this and #1156 might be of interest to you as well given your comments in httpwg/http-core.)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/472#issuecomment-772341591