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
Copy file name to clipboardExpand all lines: docs-aspnet/html-helpers/helper-basics/content-security-policy.md
+13-3Lines changed: 13 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -9,17 +9,27 @@ position: 6
9
9
10
10
# Content Security Policy
11
11
12
-
[Content Security Policy (CSP)](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) is a supplementary security approach which helps you detect and handle specific security attacks such as Cross-Site Scripting (XSS) and data-injection ones.
12
+
[Content Security Policy (CSP)](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) is a supplementary security approach which helps you prevent specific security attacks such as Cross-Site Scripting (XSS) and data-injections.
13
+
14
+
>tipAs of R3 2023, {{ site.product }} is fully compatible with strict Content Security Policy. The `unsafe-inline` keyword is no longer required in the "style-src" directive.
15
+
16
+
The following code shows how to turn on the strict CSP mode:
If the strict CSP mode is enabled, some browser features are disabled by default:
15
23
16
-
* Inline JavaScript, such as `<script></script>`, or DOM event attributes, such as `onclick`, are blocked. All script code must live in separate files that are served from the allow-listed domain.
24
+
* Inline JavaScript and CSS, such as `<script></script>`, `<style></style>`, or DOM event attributes, such as `onclick`, are blocked. All JavaScript and CSS code must live in separate files that are served from the allow-listed domain.
17
25
18
26
* Dynamic code evaluation through `eval()` and string arguments for both `setTimeout` and `setInterval` are blocked.
19
27
20
28
## (For R1 2023 SP1 and Later) Working with Telerik UI for {{ site.framework }} Components
21
29
22
-
As of R1 2023 release, the Kendo UI scripts address the `unsafe-eval` directive for all components except for the [Spreadsheet](https://docs.telerik.com/kendo-ui/controls/spreadsheet/overview). For the bigger part of its core engine, the Kendo UI for jQuery Spreadsheet uses the `Function` evaluation, and rewriting the logic of the component will lead to a great number of breaking changes.
30
+
As of R1 2023 release, the Kendo UI scripts address the `unsafe-eval` directive for all components except for the [Spreadsheet](https://docs.telerik.com/kendo-ui/controls/spreadsheet/overview).
31
+
32
+
> For the bigger part of its core engine, the Kendo UI for jQuery Spreadsheet uses the `Function` evaluation, and rewriting the logic of the component will lead to a great number of breaking changes.
23
33
24
34
The rest of the Kendo UI components and internal mechanisms have been rewritten to discard the usage of the `eval()` and `new Function()` calls.
Copy file name to clipboardExpand all lines: docs/intro/installation/using-license-code.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ position: 5
8
8
9
9
# Setting Up the License File
10
10
11
-
Using any Kendo UI for jQuery scripts that are [installed through NPM]({% slug kendoui_npm_packages_kendoui_installation %}), imported through the [Kendo UI CDN]({% slug kendoui_cdn_services_installation %}), or downloaded as trial bundles requires you to provide a personal license file. Follow the steps in this article to download a license file, add it to your application, and then reference it.
11
+
Using any Kendo UI for jQuery scripts that are [installed through NPM]({% slug kendoui_npm_packages_kendoui_installation %}) or imported through the [Kendo UI CDN]({% slug kendoui_cdn_services_installation %})requires you to provide a license file. Follow the steps in this article to download a license file, add it to your application, and then reference it.
12
12
13
13
Providing a license file is not required when using distribution methods such as NuGet, Bower, and locally downloaded Kendo UI commercial bundles.
0 commit comments