Hi, Exactly that's the reason, why I did recommend you previously to compare what the browser does compared to your curl requests.
Your browser will most likely include several additional headers: accept, authorization, Cookie, User-Agent, The new secure user agent strings (although not many servers check it yet) Your curl requests most likely do not include those headers or if it does it may include the headers in a form the server blocks. You can check what your curl is sending either using -v (--verbose) or by using a proxy with debugging capabilities. Check the response your browser receives. It may include a "set-cookie" response header, which you most likely ignore with current scripts unless you used the cookie related parameters in curl. Tell your script to send proper headers. Otherwise you will always be blocked. Good luck, Bastian On Tue, Oct 28, 2025, 12:32 ToddAndMargo via curl-users < [email protected]> wrote: > Hi All, > > There are two curl-impersonate's out there. > The first is lwthiker's and it is poorly > maintained > > https://github.com/lwthiker/curl-impersonate > > Web sites I have used it on only allow once, then > your get froze out. You have to change scripts. > It is like the other end is learning you. And > the other end eventually learns all the scrips. > > The other that is lexiforest's. It is maintained, > actually works, and works well is > > https://github.com/lexiforest/curl-impersonate > https://github.com/lexiforest/curl-impersonate/releases > > HTH someone else, > -T > > -- > Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-users > Etiquette: https://curl.se/mail/etiquette.html >
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-users Etiquette: https://curl.se/mail/etiquette.html
