The discussion revolves around an unusual and excessive number of HTTP GET requests to the kernel.org website, specifically a log entry that appears over 56 million times in a single day. K. Ryabitsev, the original poster, speculates that these requests are likely from a mobile application or device performing connectivity checks, as they consistently receive a 301 redirect response.
Participants in the conversation suggest various approaches to mitigate the issue, including:
Redirecting Traffic: One user proposes routing the traffic through a CDN to manage the load better.
Blocking Requests: Several participants suggest blocking requests from the specific user agent (okhttp/4.9.0) or implementing timeout strategies to make the connectivity checks ineffective.
Analyzing Traffic: Suggestions include using tools like Wireshark to analyze the traffic and identify the source devices or applications.
Testing Responses: Some participants recommend returning different HTTP status codes (like 404 or 429) to see how the requesting applications respond, potentially leading to bug reports from users or developers.
Identifying the Source: There are discussions about the possibility of this traffic being linked to a popular Android app or a botnet, with suggestions to check for patterns in the requests or to reach out to the okhttp library maintainers for insights.
Overall, the conversation highlights the challenges of managing unexpected traffic to a website and the collaborative effort to find a solution.
# sum up of the discussion
Posté par steph1978 . En réponse au lien That’s about 700 times a second. Évalué à -10.
The discussion revolves around an unusual and excessive number of HTTP GET requests to the kernel.org website, specifically a log entry that appears over 56 million times in a single day. K. Ryabitsev, the original poster, speculates that these requests are likely from a mobile application or device performing connectivity checks, as they consistently receive a 301 redirect response.
Participants in the conversation suggest various approaches to mitigate the issue, including:
Overall, the conversation highlights the challenges of managing unexpected traffic to a website and the collaborative effort to find a solution.