Skip to content
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

Yahoo Finance Errors out with 'Header Value too Long' #121

Open
mdframe opened this issue Mar 1, 2024 · 4 comments
Open

Yahoo Finance Errors out with 'Header Value too Long' #121

mdframe opened this issue Mar 1, 2024 · 4 comments

Comments

@mdframe
Copy link

mdframe commented Mar 1, 2024

I just started receiving the following error message with Yahoo Finance, which is a really cool add-in BTW:

2024-03-01 07:05:16.156 ERROR (MainThread) [custom_components.yahoofinance.coordinator] Error accessing crumb url. 400, message='Got more than 8190 bytes (12793) when reading Header value is too long.', url=URL('https://finance.yahoo.com/quote/NQ=F')

I do not have any symbols with a 'F' in my list and this call is for a NASDAQ exchange update which I have not added anywhere. What can I do to stop this call or stop this error?

I also added my 10th stock to track and it is not showing up. Is there a limit to the number of stocks for tracking?

Thank you for this awesome add-in!

Matt

@iprak
Copy link
Owner

iprak commented Mar 6, 2024

Quote for NASDAQ is initially fetched to establish a session. The header too long error usually auto resolves.

@iprak
Copy link
Owner

iprak commented Mar 19, 2024

I have seen that header error but usually it happens the first time and then the integration recovers. I am not sure what exactly causes that long header but the underlying component aiohttp parsing the header is limited to 8190 characters (here).

The NASDAQ symbol is used to establish access credentials.

No, there is no 10 symbol limit, I have like 23 symbols. I would check Developer Tools > State and Settings > Devices & services > Entities to see if they appear there.

@iprak
Copy link
Owner

iprak commented Apr 23, 2024

The 1.2.7 release should have reduced incidents of this.

@iprak
Copy link
Owner

iprak commented May 9, 2024

@mdframe Are you still seeing this after 1.2.7 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants