Curious, but confusing. The temporary redirects (307) are surprising because we don't use them now, though we did use them a couple years ago to redirect requests to the 'current' version. Because of caching, different people were getting different incompatible modules from different versions. Instead, now we effectively do the redirect via the browser by explicitly loading the right files. No http redirects are involved. So where are they coming from?
For each page, there should only be one load of the top-level charts/loader.js, and one version-specific loader. If there is more than one load of the loader, with inconsistent loading patterns, that could explain occasional failures. On Tue, Jul 2, 2019 at 9:37 AM James Handley <[email protected]> wrote: > Dear Daniel, > > I've managed to get hold of a screenshot of network debug from the > customer machine, and while on this occasion it did manage to load the > charts, the network traffic looked very different from what I see when I > access the app. > > When I load it I get: > > - loader.js 200 [MainPage.html] (url is > https://www.gstatic.com/charts/loader.js) > - loader.js 200 [loader.js] (url is > https://www.gstatic.com/charts/46.2/loader.js) > > The client however shows: > > - loader.js 307 341 bytes [MainPage.html] (url > is https://www.gstatic.com/charts/loader.js) > - auD?origurl=http... 307 557 bytes [loader.js] (don't know > url, except it contains 'gstatic') > - loader.js?_sm_au_=... 307 349 bytes [auD] (don't know url, except > it contains 'gstatic') > - loader.js 200 42... [loader.js] (url is > https://www.gstatic.com/charts/loader.js) > - loader.js 200 376 bytes [loader.js:..] (url is > https://www.gstatic.com/charts/46.2/loader.js) > > I'm sorry I don't have the full details of the URLs - I only have a > screenshot. > > I'm not sure what exacly is going on with the 307 responses, or the auD, > but it could explain why the google.charts.load call is happening before > the final 'loader.js' call is complete, in which case the test/timeout loop > should resolve it? > > -- > 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 [email protected]. > To post to this group, send email to > [email protected]. > Visit this group at > https://groups.google.com/group/google-visualization-api. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-visualization-api/0e9270ff-5424-4ffa-958e-72f3c34c23a2%40googlegroups.com > <https://groups.google.com/d/msgid/google-visualization-api/0e9270ff-5424-4ffa-958e-72f3c34c23a2%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2> [email protected] <[email protected]> Cambridge MA -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-visualization-api. To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJN2rvXzC1aWuss4bXSgiPGLbcqsBDMFJUhPUQsph1c3gQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
