When accessing the RealMadrid website to purchase tickets, there is a rapid blocking of requests due to the application of rate-limiting. The problem manifests itself after just 2-3 page refreshes, regardless of the use of proxies or various bypass techniques. Interestingly, when using the Firefox browser, such problems do not occur, but with the Chrome browser, the issue is present.
Current environment:
- PHP, Laravel, Selenium are used.
- Proxies for IP address rotation.
- Various fingerprinting techniques are used.
- Problems arise only in Google Chrome, while Firefox works without issues.
Task:
- Find and implement a solution to bypass rate-limiting when using Google Chrome.
- Investigate possible reasons for blocking by RealMadrid when using Chrome (possibly issues with headers, cookies, JavaScript challenges, or other protection mechanisms).
- Analyze the differences between Firefox and Chrome in terms of working with protections.
- Propose solutions for stable operation with the website without blocking.
Key requirements:
- Support for the use of proxy servers.
- Use techniques to bypass protections that minimize blocking.
- Support a strategy for working with the website in Google Chrome without violating rate-limiting.
- Resolve the issue with using the Chrome browser, similar to how Firefox operates.
P.S. We understand that sending requests to the site rate limit is a common thing, but not after 2 requests, especially since there is no such problem in Firefox
Please suggest a price, I have set a base
