Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • 12-9-stable
  • 12-7-stable
  • 12-6-stable
  • 12-8-stable
  • github/fork/Kloppi313/patch-1
  • 12-5-stable
  • 12-4-stable
  • github/fork/ramalokesh8477/master
  • 12-1-stable
  • 12-2-stable
  • 12-0-stable
  • 12-3-stable
  • 42-42-stable
  • github/fork/hussamgit398/patch-2
  • 12-3-auto-deploy-20190911
  • 12-3-auto-deploy-20190916
  • 12-3-auto-deploy-20190908
  • 12-3-auto-deploy-20190901
  • 12-3-auto-deploy-20190901-32664
  • v12.10.0.pre
  • v12.9.0
  • v12.9.0-rc42
  • v12.8.7
  • v12.8.6
  • v12.8.5
  • v12.8.4
  • v12.8.3
  • v12.6.8
  • v12.7.7
  • v12.8.2
  • v12.8.1
  • v12.9.0.pre
  • v12.8.0
  • v12.8.0-rc42
  • v12.5.10
  • v12.7.6
  • v12.6.7
  • v12.7.5
  • v12.5.9
40 results

1_settings.rb

  • Stan Hu's avatar
    5fbbd3dd
    Add support for Content-Security-Policy · 5fbbd3dd
    Stan Hu authored and Ash McKenzie's avatar Ash McKenzie committed
    A nonce-based Content-Security-Policy thwarts XSS attacks by allowing
    inline JavaScript to execute if the script nonce matches the header
    value. Rails 5.2 supports nonce-based Content-Security-Policy headers,
    so provide configuration to enable this and make it work.
    
    To support this, we need to change all `:javascript` HAML filters to the
    following form:
    
    ```
    = javascript_tag nonce: true do
      :plain
        ...
    ```
    
    We use `%script` throughout our HAML to store JSON and other text, but
    since this doesn't execute, browsers don't appear to block this content
    from being used and require the nonce value to be present.
    Add support for Content-Security-Policy
    Stan Hu authored and Ash McKenzie's avatar Ash McKenzie committed
    A nonce-based Content-Security-Policy thwarts XSS attacks by allowing
    inline JavaScript to execute if the script nonce matches the header
    value. Rails 5.2 supports nonce-based Content-Security-Policy headers,
    so provide configuration to enable this and make it work.
    
    To support this, we need to change all `:javascript` HAML filters to the
    following form:
    
    ```
    = javascript_tag nonce: true do
      :plain
        ...
    ```
    
    We use `%script` throughout our HAML to store JSON and other text, but
    since this doesn't execute, browsers don't appear to block this content
    from being used and require the nonce value to be present.