error 429, but requests executes the request correctly [duplicate] #9300
-
I previously asked this question, they told me that when responding, the server returns a response with the
By the way, I made exactly the same request on urlib3, the result is the same as requests, there are no Retry-After headers in the response, which allows you to make an unlimited* number of requests. The solution to simply delay for the time specified in the Retry-After header does not suit me (as other libraries allow you to easily make an unlimited* number of requests) Python 3.12 |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 6 replies
-
Install netcat and run |
Beta Was this translation helpful? Give feedback.
-
for example, the httpx library returns 200, again despite the fact that the headers, ip, cookies (there are none) are the same.
There's clearly something wrong with aiohttp... |
Beta Was this translation helpful? Give feedback.
OK, figured it out for you. Honestly, such a stupid bloody firewall...
This (a very sensible default) trips the firewall. It seems that accepting a connection with multiple valid TLS versions with an upper limit of 1.3 (despite the server itself doing this) is unacceptable. So, the difference might be that requests and httpx don't support TLS 1.3?
Any of these work fine: