Feature #9117
Update to secure_headers 3.x
Description
secure_headers 2.x is out. I haven't really worked out what the difference between 1.x and 2.x is though, since the changelog's been removed.
Related issues
Associated revisions
refs #9117 - update secure_headers to 3.4
History
#1
Updated by Dominic Cleal over 4 years ago
Updated by - Subject changed from Update to secure_headers 2.x to Update to secure_headers 3.x
#2
Updated by Tomer Brisker over 4 years ago
Updated by - Status changed from New to Assigned
- Assignee set to Tomer Brisker
#3
Updated by The Foreman Bot over 4 years ago
Updated by - Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3756 added
#4
Updated by Tomer Brisker over 4 years ago
- Target version set to 1.6.2
#5
Updated by Anonymous about 4 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 5a368d8129bccdd8b8b6e2599c256d42682c80b7.
#6
Updated by Dominic Cleal about 4 years ago
- Legacy Backlogs Release (now unused) set to 189
#7
Updated by Tomer Brisker about 4 years ago
- Related to Bug #16566: secure headers should allow inline images in css added
#8
Updated by Dominic Cleal about 4 years ago
- Related to Bug #17084: Webpack dev server missing from CSP on "Welcome" pages added
Fixes #9117 - Upgrade secure_headers to version 3.4
Any plugin that makes changes to secure headers may need to be updated
to correctly handle this upgrade, as there have been some breaking
changes to the secure_headers api.