Skip to content

fix: add a content security policy to the API Catalog for enhanced security - #4926

Draft
iansergeant42 wants to merge 3 commits into
v3.x.xfrom
reboot/fix-catalog-headers
Draft

fix: add a content security policy to the API Catalog for enhanced security#4926
iansergeant42 wants to merge 3 commits into
v3.x.xfrom
reboot/fix-catalog-headers

Conversation

@iansergeant42

Copy link
Copy Markdown
Contributor

Description

The security on page apicatalog/ui/v1/index.html can be improved.

This change adds a content security policy.

Type of change

  • fix: Bug fix (non-breaking change which fixes an issue)

Checklist:

  • My code follows the style guidelines of this project
  • PR title conforms to commit message guideline ## Commit Message Structure Guideline
  • I have commented my code, particularly in hard-to-understand areas. In JS I did provide JSDoc
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • The java tests in the area I was working on leverage @nested annotations
  • Any dependent changes have been merged and published in downstream modules

For more details about how should the code look like read the Contributing guideline

Signed-off-by: Ian Sergeant <ian.sergeant@broadcom.com>
@iansergeant42 iansergeant42 changed the title Add a content security policy to the API Catalog for enhanced security fix: add a content security policy to the API Catalog for enhanced security Aug 28, 2026
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants