Mixing
Hardcopy of CDN assests , security , Production
I have dotnet core server and I want to get jQuery and bootstrap files.
My question is: on a Production grad software, can I use hard-copy and the server will update the hard-copy of the files on a daily basis from Microsoft CDN or should i follow the warning and let the client get his copy direct form the CDN?
Is there a security issue when using this method?
https://docs.microsoft.com/en-us/aspnet/ajax/cdn/overview
Warning :
Production applications should not take a hard dependency on CDN assets. Applications should test for the CDN asset referenced, and use a fallback asset when the CDN is not available.
jquery security .net-core production microsoft-cdn
edited Jan 8 at 21:42
marc_s
581k13011211268
asked Jan 1 at 22:03
dxfosodxfoso
814
add a comment |
I have dotnet core server and I want to get jQuery and bootstrap files.
My question is: on a Production grad software, can I use hard-copy and the server will update the hard-copy of the files on a daily basis from Microsoft CDN or should i follow the warning and let the client get his copy direct form the CDN?
Is there a security issue when using this method?
https://docs.microsoft.com/en-us/aspnet/ajax/cdn/overview
Warning :
Production applications should not take a hard dependency on CDN assets. Applications should test for the CDN asset referenced, and use a fallback asset when the CDN is not available.
jquery security .net-core production microsoft-cdn
edited Jan 8 at 21:42
marc_s
581k13011211268
asked Jan 1 at 22:03
dxfosodxfoso
814
Using a CDN is not a security risk but it does mean your application wont work properly if the CDN provider is down (shouldnt happen but it does). If you want to avoid using a CDN, simply go to the CDN link you have, copy the text, save it to a file, and include that file in your app. This will not "autoupdate" the file as you've asked for, but IMHO autoupdating a dependency like jQuery is a decidedly BAD idea as doing so daily will almost certainly break your application at some point. Other libraries you use depend on that version, changing such things should be done with caution and tested
– DelightedD0D
Jan 2 at 0:31
FYI, the CDN files you speak of should NEVER change. CDN files are meant to remain constant always. If the library is updated, an NEW CDN file with a new name (probably with an updated version number) will be created but the old file will still be there with the old name and the same content
– DelightedD0D
Jan 2 at 0:37
Thanks for your time , but what is the meaning of hard dependency on CDN assets? can you explain please
– dxfoso
Jan 2 at 9:58
1
can you make your comment as an answer.
– dxfoso
Jan 2 at 10:02
add a comment |
I have dotnet core server and I want to get jQuery and bootstrap files.
My question is: on a Production grad software, can I use hard-copy and the server will update the hard-copy of the files on a daily basis from Microsoft CDN or should i follow the warning and let the client get his copy direct form the CDN?
Is there a security issue when using this method?
https://docs.microsoft.com/en-us/aspnet/ajax/cdn/overview
Warning :
Production applications should not take a hard dependency on CDN assets. Applications should test for the CDN asset referenced, and use a fallback asset when the CDN is not available.
jquery security .net-core production microsoft-cdn
edited Jan 8 at 21:42
marc_s
581k13011211268
asked Jan 1 at 22:03
dxfosodxfoso
814
I have dotnet core server and I want to get jQuery and bootstrap files.
My question is: on a Production grad software, can I use hard-copy and the server will update the hard-copy of the files on a daily basis from Microsoft CDN or should i follow the warning and let the client get his copy direct form the CDN?
Is there a security issue when using this method?
https://docs.microsoft.com/en-us/aspnet/ajax/cdn/overview
Warning :
Production applications should not take a hard dependency on CDN assets. Applications should test for the CDN asset referenced, and use a fallback asset when the CDN is not available.
jquery security .net-core production microsoft-cdn
jquery security .net-core production microsoft-cdn
edited Jan 8 at 21:42
marc_s
581k13011211268
asked Jan 1 at 22:03
dxfosodxfoso
814
edited Jan 8 at 21:42
marc_s
581k13011211268
asked Jan 1 at 22:03
dxfosodxfoso
814
edited Jan 8 at 21:42
marc_s
581k13011211268
edited Jan 8 at 21:42
marc_s
581k13011211268
edited Jan 8 at 21:42
marc_s
581k13011211268
581k13011211268
asked Jan 1 at 22:03
dxfosodxfoso
814
asked Jan 1 at 22:03
dxfosodxfoso
814
asked Jan 1 at 22:03
dxfosodxfoso
814
814
Using a CDN is not a security risk but it does mean your application wont work properly if the CDN provider is down (shouldnt happen but it does). If you want to avoid using a CDN, simply go to the CDN link you have, copy the text, save it to a file, and include that file in your app. This will not "autoupdate" the file as you've asked for, but IMHO autoupdating a dependency like jQuery is a decidedly BAD idea as doing so daily will almost certainly break your application at some point. Other libraries you use depend on that version, changing such things should be done with caution and tested
– DelightedD0D
Jan 2 at 0:31
FYI, the CDN files you speak of should NEVER change. CDN files are meant to remain constant always. If the library is updated, an NEW CDN file with a new name (probably with an updated version number) will be created but the old file will still be there with the old name and the same content
– DelightedD0D
Jan 2 at 0:37
Thanks for your time , but what is the meaning of hard dependency on CDN assets? can you explain please
– dxfoso
Jan 2 at 9:58
1
can you make your comment as an answer.
– dxfoso
Jan 2 at 10:02
add a comment |
Using a CDN is not a security risk but it does mean your application wont work properly if the CDN provider is down (shouldnt happen but it does). If you want to avoid using a CDN, simply go to the CDN link you have, copy the text, save it to a file, and include that file in your app. This will not "autoupdate" the file as you've asked for, but IMHO autoupdating a dependency like jQuery is a decidedly BAD idea as doing so daily will almost certainly break your application at some point. Other libraries you use depend on that version, changing such things should be done with caution and tested
– DelightedD0D
Jan 2 at 0:31
FYI, the CDN files you speak of should NEVER change. CDN files are meant to remain constant always. If the library is updated, an NEW CDN file with a new name (probably with an updated version number) will be created but the old file will still be there with the old name and the same content
– DelightedD0D
Jan 2 at 0:37
Thanks for your time , but what is the meaning of hard dependency on CDN assets? can you explain please
– dxfoso
Jan 2 at 9:58
1
can you make your comment as an answer.
– dxfoso
Jan 2 at 10:02
Using a CDN is not a security risk but it does mean your application wont work properly if the CDN provider is down (shouldnt happen but it does). If you want to avoid using a CDN, simply go to the CDN link you have, copy the text, save it to a file, and include that file in your app. This will not "autoupdate" the file as you've asked for, but IMHO autoupdating a dependency like jQuery is a decidedly BAD idea as doing so daily will almost certainly break your application at some point. Other libraries you use depend on that version, changing such things should be done with caution and tested
– DelightedD0D
Jan 2 at 0:31
Using a CDN is not a security risk but it does mean your application wont work properly if the CDN provider is down (shouldnt happen but it does). If you want to avoid using a CDN, simply go to the CDN link you have, copy the text, save it to a file, and include that file in your app. This will not "autoupdate" the file as you've asked for, but IMHO autoupdating a dependency like jQuery is a decidedly BAD idea as doing so daily will almost certainly break your application at some point. Other libraries you use depend on that version, changing such things should be done with caution and tested
– DelightedD0D
Jan 2 at 0:31
FYI, the CDN files you speak of should NEVER change. CDN files are meant to remain constant always. If the library is updated, an NEW CDN file with a new name (probably with an updated version number) will be created but the old file will still be there with the old name and the same content
– DelightedD0D
Jan 2 at 0:37
FYI, the CDN files you speak of should NEVER change. CDN files are meant to remain constant always. If the library is updated, an NEW CDN file with a new name (probably with an updated version number) will be created but the old file will still be there with the old name and the same content
– DelightedD0D
Jan 2 at 0:37
Thanks for your time , but what is the meaning of hard dependency on CDN assets? can you explain please
– dxfoso
Jan 2 at 9:58
Thanks for your time , but what is the meaning of hard dependency on CDN assets? can you explain please
– dxfoso
Jan 2 at 9:58
1
1
can you make your comment as an answer.
– dxfoso
Jan 2 at 10:02
can you make your comment as an answer.
– dxfoso
Jan 2 at 10:02
add a comment |
1 Answer
1
active
oldest
votes
Using a CDN isn't a security risk but it does mean your application wont work properly if the CDN provider is down (shouldn't happen often but can happen).
For why you would or wouldn't want to use a CDN, I'll defer to more informed folks
If you decide you want to avoid using a CDN, simply go to the CDN link you have, copy the text, save it to a file, and include that file in your app. Point all your links to this file instead of the CDN.
This will not "autoupdate" the file as you've asked for, but IMHO auto-updating a dependency like jQuery is a decidedly bad idea as doing so daily will almost certainly break your application at some point. Other libraries you use depend on specific versions of things, changing a dependency like that should be done with caution and tested thoroughly before release, definitely not via an automated process.
FYI, the CDN files you speak of should NEVER change. That is https://ajax.aspnetcdn.com/ajax/jQuery/jquery-3.3.1.min.js will never change. The file content from CDN files are meant to remain constant always. If the library is updated, an NEW CDN file with a new name (probably with an updated version number) will be created but the old file will still be there with the old name and the same content.
Regarding this bit:
Warning : Production applications should not take a hard dependency on CDN assets. Applications should test for the CDN asset referenced, and use a fallback asset when the CDN is not available.
Basically, this seems to be saying, "Don't design you application where it simply links to the CDN file and if the file is not present, your app fails. Instead, link to the CDN but your code should check that that CDN file was loaded and if not, try to load it from a different location.
Personally, I prefer a local copy of the needed file (preferably minified) in most cases and avoid CDNs, unless I'm building something that has a specific need to keep the total project size as small as possible.
answered Jan 3 at 6:55
DelightedD0DDelightedD0D
12.1k155394
@dxfoso Happy to help :)
– DelightedD0D
Jan 3 at 13:17
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53999287%2fhardcopy-of-cdn-assests-security-production%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Using a CDN isn't a security risk but it does mean your application wont work properly if the CDN provider is down (shouldn't happen often but can happen).
For why you would or wouldn't want to use a CDN, I'll defer to more informed folks
If you decide you want to avoid using a CDN, simply go to the CDN link you have, copy the text, save it to a file, and include that file in your app. Point all your links to this file instead of the CDN.
This will not "autoupdate" the file as you've asked for, but IMHO auto-updating a dependency like jQuery is a decidedly bad idea as doing so daily will almost certainly break your application at some point. Other libraries you use depend on specific versions of things, changing a dependency like that should be done with caution and tested thoroughly before release, definitely not via an automated process.
FYI, the CDN files you speak of should NEVER change. That is https://ajax.aspnetcdn.com/ajax/jQuery/jquery-3.3.1.min.js will never change. The file content from CDN files are meant to remain constant always. If the library is updated, an NEW CDN file with a new name (probably with an updated version number) will be created but the old file will still be there with the old name and the same content.
Regarding this bit:
Warning : Production applications should not take a hard dependency on CDN assets. Applications should test for the CDN asset referenced, and use a fallback asset when the CDN is not available.
Basically, this seems to be saying, "Don't design you application where it simply links to the CDN file and if the file is not present, your app fails. Instead, link to the CDN but your code should check that that CDN file was loaded and if not, try to load it from a different location.
Personally, I prefer a local copy of the needed file (preferably minified) in most cases and avoid CDNs, unless I'm building something that has a specific need to keep the total project size as small as possible.
answered Jan 3 at 6:55
DelightedD0DDelightedD0D
12.1k155394
@dxfoso Happy to help :)
– DelightedD0D
Jan 3 at 13:17
add a comment |
Using a CDN isn't a security risk but it does mean your application wont work properly if the CDN provider is down (shouldn't happen often but can happen).
For why you would or wouldn't want to use a CDN, I'll defer to more informed folks
If you decide you want to avoid using a CDN, simply go to the CDN link you have, copy the text, save it to a file, and include that file in your app. Point all your links to this file instead of the CDN.
This will not "autoupdate" the file as you've asked for, but IMHO auto-updating a dependency like jQuery is a decidedly bad idea as doing so daily will almost certainly break your application at some point. Other libraries you use depend on specific versions of things, changing a dependency like that should be done with caution and tested thoroughly before release, definitely not via an automated process.
FYI, the CDN files you speak of should NEVER change. That is https://ajax.aspnetcdn.com/ajax/jQuery/jquery-3.3.1.min.js will never change. The file content from CDN files are meant to remain constant always. If the library is updated, an NEW CDN file with a new name (probably with an updated version number) will be created but the old file will still be there with the old name and the same content.
Regarding this bit:
Warning : Production applications should not take a hard dependency on CDN assets. Applications should test for the CDN asset referenced, and use a fallback asset when the CDN is not available.
Basically, this seems to be saying, "Don't design you application where it simply links to the CDN file and if the file is not present, your app fails. Instead, link to the CDN but your code should check that that CDN file was loaded and if not, try to load it from a different location.
Personally, I prefer a local copy of the needed file (preferably minified) in most cases and avoid CDNs, unless I'm building something that has a specific need to keep the total project size as small as possible.
answered Jan 3 at 6:55
DelightedD0DDelightedD0D
12.1k155394
@dxfoso Happy to help :)
– DelightedD0D
Jan 3 at 13:17
add a comment |
Using a CDN isn't a security risk but it does mean your application wont work properly if the CDN provider is down (shouldn't happen often but can happen).
For why you would or wouldn't want to use a CDN, I'll defer to more informed folks
If you decide you want to avoid using a CDN, simply go to the CDN link you have, copy the text, save it to a file, and include that file in your app. Point all your links to this file instead of the CDN.
This will not "autoupdate" the file as you've asked for, but IMHO auto-updating a dependency like jQuery is a decidedly bad idea as doing so daily will almost certainly break your application at some point. Other libraries you use depend on specific versions of things, changing a dependency like that should be done with caution and tested thoroughly before release, definitely not via an automated process.
FYI, the CDN files you speak of should NEVER change. That is https://ajax.aspnetcdn.com/ajax/jQuery/jquery-3.3.1.min.js will never change. The file content from CDN files are meant to remain constant always. If the library is updated, an NEW CDN file with a new name (probably with an updated version number) will be created but the old file will still be there with the old name and the same content.
Regarding this bit:
Warning : Production applications should not take a hard dependency on CDN assets. Applications should test for the CDN asset referenced, and use a fallback asset when the CDN is not available.
Basically, this seems to be saying, "Don't design you application where it simply links to the CDN file and if the file is not present, your app fails. Instead, link to the CDN but your code should check that that CDN file was loaded and if not, try to load it from a different location.
Personally, I prefer a local copy of the needed file (preferably minified) in most cases and avoid CDNs, unless I'm building something that has a specific need to keep the total project size as small as possible.
answered Jan 3 at 6:55
DelightedD0DDelightedD0D
12.1k155394
Using a CDN isn't a security risk but it does mean your application wont work properly if the CDN provider is down (shouldn't happen often but can happen).
For why you would or wouldn't want to use a CDN, I'll defer to more informed folks
If you decide you want to avoid using a CDN, simply go to the CDN link you have, copy the text, save it to a file, and include that file in your app. Point all your links to this file instead of the CDN.
This will not "autoupdate" the file as you've asked for, but IMHO auto-updating a dependency like jQuery is a decidedly bad idea as doing so daily will almost certainly break your application at some point. Other libraries you use depend on specific versions of things, changing a dependency like that should be done with caution and tested thoroughly before release, definitely not via an automated process.
FYI, the CDN files you speak of should NEVER change. That is https://ajax.aspnetcdn.com/ajax/jQuery/jquery-3.3.1.min.js will never change. The file content from CDN files are meant to remain constant always. If the library is updated, an NEW CDN file with a new name (probably with an updated version number) will be created but the old file will still be there with the old name and the same content.
Regarding this bit:
Warning : Production applications should not take a hard dependency on CDN assets. Applications should test for the CDN asset referenced, and use a fallback asset when the CDN is not available.
Basically, this seems to be saying, "Don't design you application where it simply links to the CDN file and if the file is not present, your app fails. Instead, link to the CDN but your code should check that that CDN file was loaded and if not, try to load it from a different location.
Personally, I prefer a local copy of the needed file (preferably minified) in most cases and avoid CDNs, unless I'm building something that has a specific need to keep the total project size as small as possible.
answered Jan 3 at 6:55
DelightedD0DDelightedD0D
12.1k155394
edited Jan 3 at 7:04
answered Jan 3 at 6:55
DelightedD0DDelightedD0D
12.1k155394
answered Jan 3 at 6:55
DelightedD0DDelightedD0D
12.1k155394
answered Jan 3 at 6:55
DelightedD0DDelightedD0D
12.1k155394
12.1k155394
@dxfoso Happy to help :)
– DelightedD0D
Jan 3 at 13:17
add a comment |
@dxfoso Happy to help :)
– DelightedD0D
Jan 3 at 13:17
@dxfoso Happy to help :)
– DelightedD0D
Jan 3 at 13:17
@dxfoso Happy to help :)
– DelightedD0D
Jan 3 at 13:17
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53999287%2fhardcopy-of-cdn-assests-security-production%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Using a CDN is not a security risk but it does mean your application wont work properly if the CDN provider is down (shouldnt happen but it does). If you want to avoid using a CDN, simply go to the CDN link you have, copy the text, save it to a file, and include that file in your app. This will not "autoupdate" the file as you've asked for, but IMHO autoupdating a dependency like jQuery is a decidedly BAD idea as doing so daily will almost certainly break your application at some point. Other libraries you use depend on that version, changing such things should be done with caution and tested
– DelightedD0D
Jan 2 at 0:31
FYI, the CDN files you speak of should NEVER change. CDN files are meant to remain constant always. If the library is updated, an NEW CDN file with a new name (probably with an updated version number) will be created but the old file will still be there with the old name and the same content
– DelightedD0D
Jan 2 at 0:37
Thanks for your time , but what is the meaning of hard dependency on CDN assets? can you explain please
– dxfoso
Jan 2 at 9:58
1
can you make your comment as an answer.
– dxfoso
Jan 2 at 10:02