The interface has been in padding state all the time, without timeout, it will jam directly.

for example, there is no problem with an online bug, in the test environment, the request parameters are normal, and the interface does not return anything (because it has always been in the state of padding, and the debugger is directly jammed). Which boss knows what the reason is

clipboard.png


debug the background interface to see where the error is reported. Now the backstage must be dead.


there are many reasons:

  1. Server is under too much pressure, request is waiting
  2. large amount of database data, slow query
  3. request blocking due to network reasons

.


status is already 200 . Is it possible that there is too much online data and response body is too large, causing the browser to parse to Json too slowly and directly jam?

Menu