Home/ Questions/Is it okay to fix the err_spdy_ping_failed problem?
Next
Answered
Ophelia O'Brien
  • 23
Asked: 2022-05-18T21:43:02+00:00 In:

Is it okay to fix the err_spdy_ping_failed problem?

  • 23

. Advertisement .

..3..

. Advertisement .

..4..

I am working with javascript and getting the error message:

ERR_SPDY_PING_FAILED

Here is the detail of the code that I ran:

Provisional headers are shown
 Accept: application/json
 Cache-Control: no-cache
 Content-Type: multipart/form-data; boundary=----WebKitFormBoundary4sLYTyIwAAXnftvv
 Origin: https://www.example.com
 Referer: https://www.example.com/upload/document
 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36
 X-Requested-With: XMLHttpRequest
 ------WebKitFormBoundary4sLYTyIwAAXnftvv
 Content-Disposition: form-data; name="_token"
 
 GiY0lmkggP4hlyhunGRQOOBa1k1dqsr44ZgHA41e
 ------WebKitFormBoundary4sLYTyIwAAXnftvv
 Content-Disposition: form-data; name="file[0]"; filename="sdf_brz_lin.1.jpg"
 Content-Type: image/jpeg
 
 
 ------WebKitFormBoundary4sLYTyIwAAXnftvv--
$(document).ready(function() {
  $.keepalive = 
  setInterval(function() {
  $.ajax({
  url: '/ping.html',
  cache: false
  }); 
  }, 60000); 
 });

I need an explanation for the problems I’ve encountered. How to fix err_spdy_ping_failed?

err spdy ping failed
Share

2 Answers

  1. Best Answer
    Expert

    The cause:

    This error happens because the target of uploading HTTP2 of the server gets too-large window settings. The browser becomes suspicious since it is constantly receiving HTTP2 updates on how much the recipient has actually already received, it causes a bug. This also is a network connection problem.

    Solution:

    To avoid creating a major traffic jam, utilize the browser’s F12 network monitoring tools to reduce the upload rate to a acceptable value. In addition, let’s check your network connection to make sure that it’s okay.

    • 0

  2. One of these was just found. It was due to the HTTP2 receive window setting of the upload target server being too large.

    There were enough proxy servers or other things between the client endpoint and the server to ensure that the TCP bufferage was sufficient to absorb the entire upload but not stop it from being delivered until much later.

    The browser became bored while waiting for the completion. The browser becomes paranoid when it is bored and sends a HTTP2 ping to verify that the connection is still active. This seems to be a bug, considering it is receiving constant HTTP2 updates about how much has been received.

    The PING is placed in the same multiplexed HTTP2TCP connection as traffic and remains there until the PING limit is reached. Client loses faith in the server and terminates the connection. This is not helpful as the server is still alive.

    The browser will not be permitted to send too much traffic if the HTTP2 receive window is reduced to a reasonable value.

    If the server is unable to do this, the browser F12 network diagnostic tools can be used to throttle the upload rate until it matches the smallest bandwidth bottleneck in your chain. Traffic jams cannot form and PINGs will not timeout.

    This could be a sign of the Bufferbloat problem.

    • 22

Leave an answer

You must login to add an answer.

Need An Account,