Pitfall: in a short period of time, the browser will wait for the previous request to complete before processing the next request, leading to misleading code problems during asynchronous testing.

Example:

Tornado backend asynchronous processing (20 seconds for analog asynchronous processing)

Browser request API: http: // 192.168.1.98: 1104/test

Then open another table and request the same interface: http: // 192.168.1.98: 1104/test; (in this case, the second request cannot reach the backend, you must wait until the processing of the first request is complete before you can go to the backend .) Then, the browser will wait until the first request is complete and then process the second request. Therefore, it is best to add a different parameter http: // 192.168.1.98: 1104/test? Count = 123, let the browser think that different requests are normal.

Pitfall: in a short period of time, the browser will wait for the previous request to complete before processing the next request, leading to misleading code problems during asynchronous testing.