kotovalexarian-likes-github/rails--rails
1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Code Releases Activity
rails--rails/actionview/test/ujs/views/layouts/application.html.erb

27 lines
940 B
Text
Raw Normal View History

Add UJS tests
2016-11-25 23:42:29 -05:00
<!DOCTYPE html>
<html id="html">
<head>
<title><%= @title %></title>
Add support for automatic nonce generation for Rails UJS Because the UJS library creates a script tag to process responses it normally requires the script-src attribute of the content security policy to include 'unsafe-inline'. To work around this we generate a per-request nonce value that is embedded in a meta tag in a similar fashion to how CSRF protection embeds its token in a meta tag. The UJS library can then read the nonce value and set it on the dynamically generated script tag to enable it to execute without needing 'unsafe-inline' enabled. Nonce generation isn't 100% safe - if your script tag is including user generated content in someway then it may be possible to exploit an XSS vulnerability which can take advantage of the nonce. It is however an improvement on a blanket permission for inline scripts. It is also possible to use the nonce within your own script tags by using `nonce: true` to set the nonce value on the tag, e.g <%= javascript_tag nonce: true do %> alert('Hello, World!'); <% end %> Fixes #31689.
2018-02-16 08:21:48 -05:00
<%= csp_meta_tag %>
Add UJS tests
2016-11-25 23:42:29 -05:00
<link href="/vendor/qunit.css" media="screen" rel="stylesheet" type="text/css" media="screen, projection" />
Add jQuery to test vendor files ... so that we can run most, if not all, of rails-ujs tests without necessarily requiring an internet connection.
2017-07-20 08:32:48 -04:00
<script src="/vendor/jquery-2.2.0.js" type="text/javascript"></script>
Add support for automatic nonce generation for Rails UJS Because the UJS library creates a script tag to process responses it normally requires the script-src attribute of the content security policy to include 'unsafe-inline'. To work around this we generate a per-request nonce value that is embedded in a meta tag in a similar fashion to how CSRF protection embeds its token in a meta tag. The UJS library can then read the nonce value and set it on the dynamically generated script tag to enable it to execute without needing 'unsafe-inline' enabled. Nonce generation isn't 100% safe - if your script tag is including user generated content in someway then it may be possible to exploit an XSS vulnerability which can take advantage of the nonce. It is however an improvement on a blanket permission for inline scripts. It is also possible to use the nonce within your own script tags by using `nonce: true` to set the nonce value on the tag, e.g <%= javascript_tag nonce: true do %> alert('Hello, World!'); <% end %> Fixes #31689.
2018-02-16 08:21:48 -05:00
<%= javascript_tag nonce: true do %>
Add UJS tests
2016-11-25 23:42:29 -05:00
// This is for test in override.js.
Import rails-ujs v0.1.0 from rails/rails-ujs
2017-02-20 00:29:26 -05:00
// Must go before rails-ujs.
Test rails-ujs in our travis matrix
2017-02-21 13:41:17 -05:00
document.addEventListener('rails:attachBindings', function() {
window.Rails.linkClickSelector += ', a[data-custom-remote-link]';
Add UJS tests
2016-11-25 23:42:29 -05:00
// Hijacks link click before ujs binds any handlers
// This is only used for ctrl-clicking test on remote links
Test rails-ujs in our travis matrix
2017-02-21 13:41:17 -05:00
window.Rails.delegate(document, '#qunit-fixture a', 'click', function(e) {
Add UJS tests
2016-11-25 23:42:29 -05:00
e.preventDefault();
});
});
Add support for automatic nonce generation for Rails UJS Because the UJS library creates a script tag to process responses it normally requires the script-src attribute of the content security policy to include 'unsafe-inline'. To work around this we generate a per-request nonce value that is embedded in a meta tag in a similar fashion to how CSRF protection embeds its token in a meta tag. The UJS library can then read the nonce value and set it on the dynamically generated script tag to enable it to execute without needing 'unsafe-inline' enabled. Nonce generation isn't 100% safe - if your script tag is including user generated content in someway then it may be possible to exploit an XSS vulnerability which can take advantage of the nonce. It is however an improvement on a blanket permission for inline scripts. It is also possible to use the nonce within your own script tags by using `nonce: true` to set the nonce value on the tag, e.g <%= javascript_tag nonce: true do %> alert('Hello, World!'); <% end %> Fixes #31689.
2018-02-16 08:21:48 -05:00
<% end %>
<%= javascript_include_tag "/rails-ujs.js" %>
Add UJS tests
2016-11-25 23:42:29 -05:00
</head>
<body id="body">
<%= yield %>
</body>
</html>
Copy permalink