Home / Questions / 224697
Accepted
Diego
Asked: 2020-12-21 04:16:11 +0800 CST 2020-12-21 04:16:11 +0800 CST

net::ERR_SPDY_PROTOCOL_ERROR

  • 772

I had an API on a server which works perfectly.

When migrating it to the new server, it has stopped working for me, I continuously see the error: net::ERR_SPDY_PROTOCOL_ERRORin chrome and Solicitud de origen cruzado bloqueada: La misma política de origen no permite la lectura de recursos remotos en https://xxx. (Razón: Solicitud CORS sin éxito).

If I repeatedly press the access button, it does access, but what is happening does not make sense.

I have two hypotheses:

  1. The new server serves the content in HTTP2 and angularjs doesn't interpret it correctly
  2. The API installation was unsuccessful.

Regarding the first one, I am going to investigate how to force the server to respond in HTTP, to see if this way, at least, I solve the error, while I investigate the reason for it.

Data: It only fails with requests POST, in which GETit does not happen.

angularjs

1 Answers

  1. Best Answer

    If this has ever happened to you, in my case, it's because IIS was serving the content in HTTP 2, and even though Chrome, Firefox, etc. they were updated, they did not interpret it well.

    I have forced to return the content in HTTP and it works without problems.

    • 0