Updates to the CDN
Updates to the CDN
We're currently updating the CDN's software and are finding some users are unable to access their CDN generated downloads. If your links are no longer working please post them in this thread and we'll address them as a priority.
This discussion has been closed.
Replies
Hello, here's a link which just stopped working.
https://cdn.datatables.net/v/ju-1.12.1/jqc-1.12.3/jqc-1.12.3/dt-1.10.16/r-2.2.0/datatables.min.js
Hello, whatever change you've made, has fixed the issue, thank you.
I believe the following URL is no longer working:
https://cdn.datatables.net/v/dt/jqc-1.12.4/moment-2.13.0/selectize-0.12.1/dt-1.10.13/b-1.2.4/ef-selectize-1.5.6/fc-3.2.2/fh-3.1.2/se-1.2.0/datatables.min.js
It's been this way for several hours.
It's working now @TomBajzek , can you try again please.
Colin,
That URL is still not working here. We've cleared each repeatedly and tried various browsers. It still seems to be broken.
Tom
Colin,
This is still not working. The URL above now loads correctly if I just type it into the address field of my browser. However, my app still does not work, as it cannot find the Editor, among other things. I changed my the URL to use dt-1.10.19 instead of dt-1.10.13, and that URL also loads, but that change didn't make any difference in the outcome.
I have copied the Javascript console output from Chrome for you to see:
Uncaught TypeError: Cannot read property 'mixin' of undefined
at datatables.min.js:29
at datatables.min.js:29
at datatables.min.js:29
dataTables.buttons.min.js:5 Uncaught TypeError: Cannot read property 'ext' of undefined
at dataTables.buttons.min.js:5
at dataTables.buttons.min.js:5
at dataTables.buttons.min.js:5
buttons.colVis.min.js:1 Uncaught TypeError: Cannot read property 'ext' of undefined
at buttons.colVis.min.js:1
at buttons.colVis.min.js:1
at buttons.colVis.min.js:1
dataTables.editor.min.js:8 Uncaught Editor requires DataTables 1.10.7 or newer
table.beads.js:13 Uncaught TypeError: Cannot read property 'Editor' of undefined
at HTMLDocument.<anonymous> (table.beads.js:13)
at i (datatables.min.js:14)
at Object.fireWith [as resolveWith] (datatables.min.js:14)
at Function.ready (datatables.min.js:14)
at HTMLDocument.K (datatables.min.js:14)
I'm hoping that output gives you a clue as to the problem.
I had made a few changes to the JS code last night before the URL above failed. When it still failed today, I reverted to the previous code, which has been stable since July 22, but this failure has continued.
Can you provide a suggestion as to how to proceed? Let me know if you need to see this live.
Thanks,
Tom
Hi Tom,
Are you able to give me a login for your site so I can take a look and see what is going wrong please. As you say, the URL above appears to be working, so there is something going on that I'm not aware of.
Allan
I use SRI on my CDN downloads. Is it possible the hashes have changed? For example https://cdn.datatables.net/w/bs4/dt-1.10.18/r-2.2.2/datatables.min.css seems to have changed from
integrity="sha384-u4DrSb6HrhSJIu938tCXHkm/G9ivRb9WHcnSq+s4olYfhhCtKtS+JRx+zKOfZala"
to
integrity="sha384-fs9Oiyinnjzfo/vptmiCSlzK5HJlSKcl2/xoDEDKAiUK4wP7rRbx2oeyBt3h7Vmn"
But (for now) only some users seem to be affected (perhaps based on what cache they look at)
Hello, my CDN stopped working. Could you please send me the improved version? Thanks alot
<link rel="stylesheet" type="text/css" href="http://cdn.datatables.net/v/bs-3.3.7/jq-3.2.1/jq-3.2.1/dt-1.10.16/b-1.4.2/b-colvis-1.4.2/cr-1.4.1/fh-3.1.3/r-2.2.0/sc-1.4.3/datatables.min.css"/>
<script type="text/javascript" src="http://cdn.datatables.net/v/bs-3.3.7/jq-3.2.1/jq-3.2.1/dt-1.10.16/b-1.4.2/b-colvis-1.4.2/cr-1.4.1/fh-3.1.3/r-2.2.0/sc-1.4.3/datatables.min.js"></script>
@quangn - your URL isn't actually valid. It includes jquery twice for some reason. I guess the old version was more forgiving, but to make it work again, remove the second
jq-3.2.1:@ianmcl - We tried to maintain perfect bit compatibility between the old CDN server and how it now works, but there were a few cases whereby that wasn't possible or practical. Could you update the hashes you are using for your
integrityattributes please to be based off the current files? We are going to start publishing the SRI hashes and including them in the generated tags on our download page soon (this was actually a large part of the reason to change our CDN software).Allan
I've switched off SRI for these resources for now. That's because I wan't getting an integrity failure but some users were, and I don't want to use a new hash until I know everyone's getting the same version. I'll give it a week or two and try the new hashes then. Thanks
I’m here due to SRI hash mismatches, too. I’m now adding the new hashes, but I just want to point out that all of my CSS and JavaScript hashes have stopped matching, even for the simplest https://cdn.datatables.net/v/bs/dt-1.10.13/datatables.min.js that I use on pages that don’t need other modules.
(I know my DataTables is outdated… I should fix that sometime.)
Hi @astiob ,
It's probably just whitespace in the header knocking out the hash. It might be worth comparing your previous with the new (if you have a copy) just to confirm.
Cheers,
Colin
This one isn't working:
http://cdn.datatables.net/v/bs-3.3.7/jq-3.2.1/jq-3.2.1/dt-1.10.16/b-1.4.2/b-colvis-1.4.2/cr-1.4.1/fh-3.1.3/r-2.2.0/sc-1.4.3/datatables.min.css
http://cdn.datatables.net/v/bs-3.3.7/jq-3.2.1/jq-3.2.1/dt-1.10.16/b-1.4.2/b-colvis-1.4.2/cr-1.4.1/fh-3.1.3/r-2.2.0/sc-1.4.3/datatables.min.js
Hi @jmlange13 ,
See Allan's comment above
We're curious as to where these links are coming from? Were they from the Download page, or have you hand-crafted them?
Cheers,
Colin
These aren't working (hashes changed):
https://cdn.datatables.net/v/dt/dt-1.10.15/b-1.3.1/b-colvis-1.3.1/b-html5-1.3.1/fh-3.1.2/r-2.1.1/rg-1.0.0/datatables.min.js
https://cdn.datatables.net/v/dt/dt-1.10.15/b-1.3.1/b-colvis-1.3.1/b-html5-1.3.1/fh-3.1.2/r-2.1.1/rg-1.0.0/datatables.min.css
currently using a local copy...
Hi @dtuser2019 ,
Yep, the hashes all would have changed with the change to the CDN. Please see Allan's comment above.
Cheers,
Colin
@Colin: Thanks, have overlooked that part.
Hello!
Yesterday, these two links have stopped working:
https://cdn.datatables.net/v/dt/jszip-2.5.0/dt-1.10.18/b-1.5.4/b-flash-1.5.4/b-html5-1.5.4/fc-3.2.5/datatables.css
https://cdn.datatables.net/v/dt/jszip-2.5.0/dt-1.10.18/b-1.5.4/b-flash-1.5.4/b-html5-1.5.4/fc-3.2.5/datatables.js
Everything was working well a minute, the other, it was over...
Thank you to help me with that issue
Hi @marie-pier.plante ,
Those links are being served as expected for me - can you confirm there's a problem there still, please.
Cheers,
Colin
Hello @colin
Still not working on my side...
Hi @marie-pier.plante , When you say not working, are you getting a 404, or contents different to what you were expecting?
Hi @colin
I get a different content... I have a datagrid and since that problem, it won't load correctly.
On developper tool, I see that these files have been blocked
Hi again @colin
Here is the full line The project use
Hi @marie-pier.plante ,
Yep, as Allan said above the hashes have changed with this new CDN, so they will need to be updated. Please see his reply for the longer answer.
Cheers,
Colin
I'm impressed with those of you using
integrityfor your CDN resources - good work. Yes, per my note above, we weren't quite able to get bit matching for the updated resources, so if you are using an integrity hash it will need to be updated.We will soon be updating our download page to use SRI by default in the code it creates.
Allan
@allan Datatables is a natural fit on a checkout page with Line items etc. And a checkout page is also a target for exploits like Magecart. SRI is essential in such cases.
Hello! The SRI checks in my projects has failed too. I couldn't figure out why chrome blocked it because the shasum i generated didn't match Chrome's.
I found out that the cdn serves different content if the Origin header is set to where our site is hosted, and that doesn't make any sense to me????
Compute a sha384 for the following url:
https://cdn.datatables.net/v/bs4/dt-1.10.18/b-1.5.2/cr-1.5.0/fc-3.2.5/fh-3.1.4/kt-2.4.0/r-2.2.2/rg-1.0.3/rr-1.2.4/sc-1.5.0/sl-1.2.6/datatables.min.js
The Shasum should be: i5VhhMYF7zRALSGNqMml1dyYnRHN0ZcX3zWX24C61j2RnNRmnLNM1qhgVQ4Rsfig
Now if i set the Origin header to where my site is hosted I get another shasum:
wCnlFw+xFQERRywvuerAYA9Lan00khtuQyGuVoRJECN9Xc5Nw2BI/bZG8oUvNxfd
So the cdn gives different content for the same url based on if the origin header is set to my domain.
Why does the cdn gives me different content (different shasum) based on if the origin head is set to my domain?
And the weird thing is, I can only procude a different sum if I use my domain as origin, I havent found any other domain that produces the same result as my domain
I have absolutely no idea! Can you get me steps to reproduce the error so I can look into it please?
Allan
Yes sure, I have sent you a pm with the details! Thanks!