Recently, the test applet encountered a small problem. The rendering of the f2 chart on the IOS side of the mobile phone failed, resulting in the coordinate axis not being displayed, and the other side was normal, and it was still sporadic.
At the beginning, I fell into a blind spot of thinking, thinking about compatibility issues, it must not be a data error. Are the components incompatible? Or the rendering logic is wrong? So I went to one poor alley after another. . .
After looking at the packet capture data, I found that there was an interface prompting an illegal request. It turned out that there were multiple requests, and the timestamps were generated consistently, which was identified as an illegal request by the anti-crawling mechanism. So I analyzed the interface of each request for the following chart, and found that the front-end request interface is a bit problematic, as many charts are requested as many times, so it is because of the above reasons that the rendering cannot be rendered.
Because of the anti-climbing mechanism problem, the front end optimized the request interface, found fixed parameters, and reduced the number of requests, thereby effectively reducing the probability of illegal requests (the front end of the illegal request also handled exceptions and gave a friendly reminder , so that the interactivity of the applet will be much better). In this way, if it is not clicked multiple times within 30 milliseconds, there will be no illegal request. It is feasible under normal circumstances, so that’s it~~
Come on three times, family members, three grams of oil and three grams of oil~~ I would like to thank you here! ! !