-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FlurlHttpException with StatusCode: 429, ReasonPhrase: 'Too Many Requests' #68
Comments
Can confirm the same. Possible rate limits on the part of Yahoo, but why all of a sudden. |
Rate limit? Definitely not, as the exemption was thrown immediately after the first request. |
I am hitting the same too. |
I have found a way. Tip came from here: Do the same thing as in InitAsync() when we get the crumb:
So, both in Historical.cs and in Quote.cs, put this line before the GetAsync()
Works for me at the moment. (from the UK). One proper solution is to create the string userAgentKey/userAgentValue as data member fields somewhere, and all 3 GetAsync() could use that. |
#68 Fixed issue with missing and outdated HTTP Header
Feeds work again now, even without the change proposed above! |
Thx for checking. Maybe it works for you now without the proposed changes, but you might use it from a different country (USA?). I am from London. Let's hear the experiences of others. |
I am in Germany. It started failing last night, but it worked again about an hour ago. |
I made code changes as suggested. Please try it. |
Funny enough. 30min after my previous post (that I double-checked), now in the UK, I get the same as you: I also have the random 'Call failed with status code 401 (Unauthorized)' when we get the Crumb. Thx for sharing the experience. |
In AU I too get some random 401 |
Since last night, prices cannot be retrieved from Yahoo Finance.
The failure occurs in Yahoo - Quote.cs in the following method
Below, the FlurlHttpException ex is caught.
The message in ex contains:
The text was updated successfully, but these errors were encountered: