You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting with the **Q3 2009 Service Pack 1** release you will be able to load the controls scripts and skins from the Telerik CDN. Telerik CDN is hosted on the Amazon CloudFront service. This is a **global content delivery service** with edge locations in the US, Europe and Asia.
13
+
Telerik UI for ASP.NET AJAX supports loading control scripts and skins from the Telerik CDN. This functionality has been available since Q3 2009 SP1 and is included in all supported versions. Telerik CDN is hosted on the Amazon CloudFront service. This is a **global content delivery service** with edge locations in the US, Europe and Asia.
16
14
17
15
Using the Content Delivery Network has a number of advantages:
18
16
19
17
***Reduced latency** – requests will be automatically redirected to the nearest server
20
18
21
-
***Compressed output** - the javascript files are already compressed so they are in minimum size
22
-
23
19
***Better use of caching** – each resource only needs to be downloaded once
24
20
25
21
***Reduced hosting expenses** – we host the resources for you so you can pay less
@@ -28,15 +24,13 @@ Using the Content Delivery Network has a number of advantages:
28
24
>
29
25
30
26
31
-
32
-
33
-
**Caching** is what a CDN is all about. Say you have a number of applications that all utilize RadGrid. A customer will load the RadGrid scripts just once and then use the cached version until he clears his browser’s cache. Proxies will also aggressively cache these resources.
27
+
**Caching** is what a CDN is all about. Say you have a number of applications that all utilize RadGrid. A customer will load the RadGrid scripts just once and then use the cached version until they clear the browser cache. Proxies will also aggressively cache these resources.
34
28
35
29
## When NOT to use CDN?
36
30
37
-
* Intranet applications in particular are a bad candidate for it. Your Intranet is likely to be a lot faster than any type of CDN. You’ll also lose the ability to run your application without an Internet connection.
31
+
* Intranet scenarios often do not benefit from external CDNs, as internal networks can provide lower latency and do not depend on external connectivity.
38
32
39
-
* When you are using a latest internal build (not an official one).
33
+
* When you are using an internal build (not an official one).
40
34
41
35
## How to enable Telerik CDN
42
36
@@ -46,7 +40,6 @@ The **RadStyleSheetManager** has the same configuration for enabling the Telerik
46
40
>
47
41
* Official Major Releases
48
42
* Official Service Packs
49
-
* BETA releases>
50
43
51
44
52
45
1. Make sure you are using Telerik.Web.UI version 2009.3.1207 (**Q3 2009 SP1**) or later.
@@ -60,14 +53,15 @@ The **RadStyleSheetManager** has the same configuration for enabling the Telerik
@@ -94,138 +90,49 @@ Moreover, you can enable the CDN support **globally** by adding the following ke
94
90
````
95
91
96
92
97
-
98
93
Note, that the second line will enable the [CDN support for the CSS and image files]({%slug stylesheetmanager/cdn-support/overview%}) for the skins.
99
94
100
95
## How are my users affected?
101
96
102
-
The Telerik CDN uses the following host names for loading the control resources.
103
-
104
-
***http://aspnet-scripts.telerikstatic.com** - for the scripts;
105
-
106
-
***http://aspnet-skins.telerikstatic.com** - for the skins (css and images);
107
-
108
-
Your users need to have access to the above URLs.
109
-
110
-
>note Check the [CDN Troubleshooting - Links to web resources are non-secure although the page is requested through SSL]({%slug scriptmanager/troubleshooting/cdn%}) for issues with pages loaded over HTTPS that still request the HTTP CDN scripts.
111
-
112
-
113
-
## What about SSL?
114
-
115
-
When a SSL connection is used RadScriptManager and RadStyleSheetManager will use the native Amazon CloudFront distribution hosts:
97
+
When CDN support is enabled (`EnableCdn="true"` or `<CdnSettings TelerikCdn="Enabled" />`), the RadScriptManager and RadStyleSheetManager render CDN URLs that match the page protocol (HTTP or HTTPS). The CDN does not switch protocols on its own; the framework renders URLs based on the page request scheme, and modern browsers may upgrade requests to HTTPS (HSTS, corporate policies, etc.). Telerik provides distinct host names for each protocol.
116
98
117
-
***https://d2i2wahzwrm1n5.cloudfront.net** - for the scripts;
99
+
Active CDN host names:
118
100
119
-
***https://d35islomi5rx1v.cloudfront.net** - for the skins (css and images);
***http://aspnet-skins.telerikstatic.com** / **https://aspnet-skins.telerikstatic.com** – skins (CSS and images)
121
108
122
109
123
-
## Detailed information with an example
124
-
125
-
Let's add some RadControls on the page (RadMenu, RadTabStrip, RadListBox) and RadScriptManager with enabled CDN support. When you run the page you will observe the following:
126
-
127
-
1. RadScriptManager combined the **MicrosoftAjax.js** and **MicrosoftAjaxWebForms.js** into a single compressed axd resource.
128
-
129
-
2. The Core.js, jQuery.js and all the scripts needed for the RadControls are loaded from the CDN network. If the browser supports compression (the request has **Accept-Encoding** HTTP header set to *gzip,deflate*) then the files are served **compressed**. The compression is done before uploading of the files to the CDN network, so there are no CPU cycles on the server to compress at run-time. If the browser is **IE6** then the files are served **uncompressed** (from another URL) that is because earlier versions of the browser has problems with decompressing the output.
Note that scripts from the CDN are placed in the **/ajaxz/** folder - this means that the compressed file is downloaded. If your browser does not support content encoding (or it is IE6) then you will notice that the scripts are loaded from the **/ajax/** folder.
140
-
110
+
These CDN endpoints are certificate-enabled and served over secure HTTPS. The actual domain used is selected automatically by the framework based on protocol and browser behavior. Do not hard-code CDN URLs; always rely on the built-in CDN support.
141
111
112
+
> Note: If your environment uses firewalls, proxies, or strict corporate security policies, ensure the Telerik CDN domains are allowed. Otherwise, disable CDN support to serve resources locally.
142
113
143
114
## More Optimizations
144
115
145
-
To further optimize the load of the scripts you can download the **MicrosoftAjax.js** file from the Microsoft CDN (valid for **.NET 3.5** only):
0 commit comments