Finalized Content Security Policy Fix#1567
Open
BrianRaymond800 wants to merge 18 commits into
Open
Conversation
…d to any emotion based styles. Fixed majority of the CSP style tag problems but a few still remain. (Still in Progress)
formatting, comments, and readability.
and better clarification.
5 tasks
huss
requested changes
Feb 2, 2026
huss
left a comment
huss
left a comment
Member
There was a problem hiding this comment.
Thanks to @BrianRaymond800 for updating this work.
- There is a merge conflict in a file. I also think the branch may be out of date. Please carefully merge in development.
- When I run OED and look in the web browser console, I see a number of security content msgs. These need to be figured out. I don't know if it relates to the commented out code that was removed as noted in a comment.
- I've added some comments to consider.
| multiple sites as an exceptions would be : img-src 'self' http://example.com https://site_example.net; becomes img-src 'self' | ||
| http://example.com https://site_example.net https://newException.com; | ||
| --> | ||
|
|
Member
There was a problem hiding this comment.
A number of commented out lines were removed here from the original PR. I wanted to check if they had any value or were examples.
Author
There was a problem hiding this comment.
From what I can tell, those lines were an alternate implementation of the CSP that was rejected and replaced with the current one, but never fully removed. That is why I chose to remove it.
BrianRaymond800
force-pushed
the
pr-update
branch
from
February 12, 2026 22:54
589f9b4 to
28c2cd9
Compare
BrianRaymond800
pushed a commit
to BrianRaymond800/OED
that referenced
this pull request
Apr 5, 2026
…us with owners and upstream PR evidence • Added Owner column identifying responsible team members for each finding • Added upstream OpenEnergyDashboard PR references where fixes or work exist • Corrected Issue OpenEnergyDashboard#6 status to In Progress based on open PR OpenEnergyDashboard#1567 • Clarified findings with no assigned owner or implementation work started • Improved overall clarity and traceability of security remediation progress
This was referenced Jun 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR contains work completed by @pogoco26 and @CamClendenon, which added a Content Security Policy to OED. Information about their work can be found in PR #1484. Since then, the code from that PR has been updated by @BrianRaymond800 to contain more comments, clarification, and general cleanup.
Type of change
Checklist
(Note what you have done by placing an "x" instead of the space in the [ ] so it becomes [x]. It is hoped you do all of them.)
Limitations
I am not aware of any limitations, besides those that were listed in the original PR.