Query Wrapper Examples are throwing a "Request Timed Out" Error

[Avadhoot Dandekar]

All queries were working fine till few days ago. And now they are all throwing a "Request Timed Out Error". Even if you see the Miscellaneous Examples using an external Spreadsheet explained here:

https://developers.google.com/chart/interactive/docs/examples 

are also showing "Request Timed Out Error". This is happening only in cases in which you query data from an external spreadsheet. 

Any idea or thoughts on this? Thanks.

[Daniel LaLiberte]

Apparently some older spreadsheet URLs are redirecting to newer ones, and the redirect process is dropping some security related headers that are required for the current way queries are being done to be more secure and faster (using XHR).  If you look in your browser's debugger console, you should be able to see the redirect in an error message, and replace the URL in your query with the new URL.  

I am debating whether to rollback the v49 release (so 'current' would again be '48') or just let everyone who needs to switch to '48'.  This won't be easy to fix from the Google Charts side, and the redirects on the spreadsheets side may also be difficult if not impossible to change.   At best, we could check whether the URL looks like it requires the older query mechanism, which may fail on IE11 or Edge (which was one of the motivations for the change).  

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualizati...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/e4219a21-cd5a-4670-84cb-2f709be03f75n%40googlegroups.com.

--

Daniel LaLiberte

dlaliberte@Google.com   Cambridge MA

[Avadhoot Dandekar]

Hello Daniel,

Anything further on this because all embedded queries are crashing. Even the examples explained in the Examples section of the documentation also show the same error. What is the advice to users?? Hoping for some kind of relief. Thanks.

[Avadhoot Dandekar]

Hi Daniel,

Thank you man. Thank you for making it work for '48' so that we could switch to it in the place of 'current'. Thanks again.

On Wednesday, 29 July 2020 at 21:02:53 UTC+5:30 Daniel LaLiberte wrote: