cdn.datatables not working

cdn.datatables not working

dalbarrandalbarran Posts: 2Questions: 1Answers: 0

Good morning, due to yesterday’s incident, we lost connection to the DataTables CDN. The issue seemed to be resolved, and gradually some of us have been able to reconnect, with the applications starting to work again — but not for everyone.

For some users, the DataTables scripts load correctly, while for others they don’t. In fact, in my own case, the application connects to the CDN when using Chrome, but not when using Firefox in incognito mode. Other users are also unable to access via Chrome or Firefox.

We also use an internal network to access the internet, and we’re not sure if that might be contributing to the problem.

Answers

  • rf1234rf1234 Posts: 3,167Questions: 92Answers: 436
    edited July 30

    In fact, in my own case, the application connects to the CDN when using Chrome, but not when using Firefox in incognito mode. Other users are also unable to access via Chrome or Firefox.

    If you can't access the files using Browser A, but you can using Browser B, this is usually due to caching of the files in the browser. I had that yesterday, too: Chrome worked and Firefox didn't - because I almost never use Firefox and nothing was cached.

    The easiest short term solution is to replace cdn.datatables.net with datatables-cdn.com After a couple of days you can revert back to be on the safe side.

  • allanallan Posts: 64,850Questions: 1Answers: 10,734 Site admin

    Hi,

    I've just written a reply to a similar topic which is relevant. As noted there I'm confident that the CDN server is responding correctly to requests that it gets, but there might be HTTP caching that is causing the problem for some clients. A force refresh or a cache busting query parameter will hopefully resolve the issue.

    Allan

  • dalbarrandalbarran Posts: 2Questions: 1Answers: 0

    The problem is that we don't import these links directly; the BootsFaces library in our Java project does it automatically when needed. We can't directly access or change the code where the import is made. Thanks for you response!

  • allanallan Posts: 64,850Questions: 1Answers: 10,734 Site admin

    That certainly complicates things. Does a ctrl-f5 force refresh help at all for the users having a problem? Or can you get them to try and load the JS file directly and see what the outcome is? Sorry, I know that asking client's to do that sort of thing is far from ideal, but the HTTP cache would need to be cleared to allow it to work for them again.

    Allan

Sign In or Register to comment.