Closed Zert closed 2 years ago
The code you linked to is for HTTP/2. The related issue is for HTTP/1.1.
Please be more specific as to which server(s) you are having this issue with, as well as which protocol is impacted exactly.
Yes, the related issue is really for HTTP/1.1, but I have that behaviour with HTTP/2 and Google servers, like www.google-analytics.com
Please be more specific. Examples of requests and/or server name and/or relevant output.
Unfortunately, I cannot repeat this case, since it is very rare. May be depends on IP address of server of something else. I've found this error in logs.
So may be it is better to patch cowlib locally in case this is not the common problem.
Yes because I need to know which servers are breaking the spec to know when I can remove the workaround again once it doesn't cause a problem anymore. But I am happy to receive further information when/if you get any and act on it.
Some servers are sending
content-length=0
header in the response with 204 code. Cowlib reset this connection with stream error: https://github.com/ninenines/cowlib/blob/master/src/cow_http2_machine.erl#L744 May be cowlib should handlecontent-length
of 204 with value 0?Similar issue in jdk: https://bugs.openjdk.java.net/browse/JDK-8218662