Add Content-Security-Policy header
All threads resolved!
All threads resolved!
Now dev testing can reproduce the security issues we saw in production.
Merge request reports
Activity
Filter activity
added 5 commits
-
6a2ef20b...221db9f2 - 4 commits from branch
pleroma:develop
- 02e6d4f0 - add csp header to dev server
-
6a2ef20b...221db9f2 - 4 commits from branch
- Resolved by HJ
i don't really understand why tho
added 12 commits
-
02e6d4f0...60b413d0 - 11 commits from branch
pleroma:develop
- 4e8a5c9f - add csp header to dev server
-
02e6d4f0...60b413d0 - 11 commits from branch
added 21 commits
-
4e8a5c9f...6b4fe1c2 - 20 commits from branch
pleroma:develop
- d8c76219 - add csp header to dev server
-
4e8a5c9f...6b4fe1c2 - 20 commits from branch
- Resolved by HJ
I just had a new feature testing in
mfc-develop
which was great until i deployed it to dev server and got a white screen because CSP violation that developer did not see because it was never deployed to a production Pleroma instance with the CSP headers enabled...edit: merged this into
mfc-develop
branch for our use, but I encourage us to do this upstream as well so these issue can be caught as early as possible in the development processEdited by feld
added 6 commits
-
d8c76219...2f875406 - 5 commits from branch
pleroma:develop
- be80a04a - add csp header to dev server
-
d8c76219...2f875406 - 5 commits from branch
added 3 commits
-
be80a04a...cf2dc5b6 - 2 commits from branch
pleroma:develop
- 34d95454 - add csp header to dev server
-
be80a04a...cf2dc5b6 - 2 commits from branch
mentioned in commit 0a7c60c3
mentioned in commit 114a36c9
mentioned in merge request !880 (merged)
Please register or sign in to reply