Timeline for answer to How to avoid HTTP error 429 (Too Many Requests) python by MRA
Current License: CC BY-SA 3.0
Post Revisions
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2021 at 5:46 | history | edited | CommunityBot |
replaced http://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc
|
|
| Aug 8, 2018 at 5:05 | review | Suggested edits | |||
| Aug 8, 2018 at 7:34 | |||||
| Apr 13, 2018 at 11:09 | comment | added | MacFreek |
Thanks @MRA. I found that the headers are available in the exception too: after catching HTTPError as my_exception, it is available in my_exception.headers, at least for urllib2.
|
|
| Apr 12, 2018 at 10:33 | comment | added | MRA | @MacFreek I don't have any particular Python code examples ready, but I assume some examples about how to retrieve response headers in general can be taken from the answers to this question: stackoverflow.com/q/843392 | |
| Apr 11, 2018 at 14:14 | comment | added | MacFreek | Thanks for mentioning the "Retry-after" header. I would love a code example to see how to get that value (I was using urllib, to OP mechanize, in either case I don't think the headers are included in the raised exception) | |
| May 23, 2016 at 10:27 | comment | added | MRA | Well, no one ever said that all web servers are configured correctly. Also, since most rate limiters are identifying visitors by IP, this might lead to problems in a scenario where IPs are shared dynamically. If you keep receiving status 429 although you are confident that you have not sent too many requests at all, you might consider contacting the site's administrator. | |
| Apr 29, 2014 at 14:14 | history | answered | MRA | CC BY-SA 3.0 |