I used Chrome's Network Log Export tool at chrome://net-export/ to see exactly what was behind the ERR_HTTP2_PROTOCOL_ERROR error.I was able to resolve this by following these steps: If the throughput on that last GIF is slowed so much that it drops below the minBytesPerSecond limit, it will cut the connection. However, this limit can also be triggered in cases where an innocent user requests many resources all at once (such as lots of images on a single page), and the server is forced to ration the bandwidth for each request so much that it causes one or more requests to drop below the throughput limit, which causes the server to cut the connection and shows up as net::ERR_HTTP2_PROTOCOL_ERROR in Chrome.įor example, if you request 11 GIF images all at once, and each individual GIF is 10 megabytes (11 * 10 = 110 megabytes total), and the server is only able to serve at 100 megabytes per second (per thread), the server will have to slow the throughput on the last GIF image until the first 10 are finished. This is to protect against "slow drip" denial of service attacks. It turns out that some web servers will cut the connection to a client if the server's data throughput to the client passes below a certain limit. This setting can be found in system.applicationHost/webLimits in IIS's Configuration Editor. The fix for me was setting minBytesPerSecond in IIS to 0. But that would mean the browser is the culprit, and then I wouldn't understand why it happens on two identical pages with one having a 200 header and the other a 404 (same goes if I disable JS).
The described behavior is the same as the one I can observe. However, for large response contents, sending a RST_STREAM may have a good chance to arrive to the server before the whole response content is sent, and therefore will save bandwidth." It is possible that by the time the RST_STREAM travels from the client to the server, the whole content of the request is in transit and will arrive to the client, which will discard it.
The connection is still usable for other requests, and requests/responses that were concurrent with the one that has been aborted may continue to progress. When the server receives a RST_STREAM, it will stop sending DATA frames to the client, thereby stopping the response (or the download). Trying to go deeper with the chrome://net-export/ and tools is telling me the request ends with a RST_STREAM : t=123354 HTTP2_SESSION_RECV_RST_STREAMįor what I read in this other post, " In HTTP/2, if the client wants to abort the request, it sends a RST_STREAM. Every other asset on the Network tab has a success return, except the whole document itself.Ī curl -head -http2 request in console returns the following success: HTTP/2 200 Even if the error is triggering on each page having a HTTP header 200, those pages are always loading on client's browser, but sometimes an element is missing (in my exemple, the external Twitter feed).
#PROJECT PLAN 365 RESOURCE DENIAL MAC#
Moreover, I noticed it appears on very recent Google Chrome releases the error doesn't pop on v.64.X, but it does on v.75+ (regardless of the OS I'm working on Mac tho). Thing is the error isn't documented at all. I was wondering if it could be related to the header returned by the server since there is this '200' mention in the error, and a 404 / 500 page isn't triggering anything. (NB: I tried with Safari, and I have a similar kcferrordomaincfnetwork 303 error) Google Chrome is the only web browser triggering the error: it works well on both Edge and Firefox. If I access the website in HTTP, the Twitter feed appears and the error disappears
#PROJECT PLAN 365 RESOURCE DENIAL CODE#
If I remove the code to load the Twitter feed, the error remains
I can notice in the console the ERR_HTTP2_PROTOCOL_ERROR My Twitter feed integrated via isn't loaded at all I can't be 100% sure it is related, but it looks like it prevents JavaScript to be executed properly.įor instance, the following scenario happens : I'm not sure exactly what can provoke this error, I just noticed it pops out only when accessing the website in HTTPS. I'm currently working on a website, which triggers a net::ERR_HTTP2_PROTOCOL_ERROR 200 error on Google Chrome.
0 kommentar(er)
