higress-group/higress

implement a wasmplugin to support Content Security Policy

Open

#1,706 opened on Jan 23, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (1,219 forks)github user discovery
help wantedlevel/easysig/wasm

Repository metrics

Stars
 (9,036 stars)
PR merge metrics
 (Avg merge 7d 9h) (18 merged PRs in 30d)

Description

Why do you need it?

内容安全策略（Content Security Policy，CSP): greatly reduce the risk of XSS attacks

How could it be?

I hope there is a plugin to help add the csp header (Content-Security-Policy).

Other related information

Related links

Contributor guide

Research direction
Explore Higress's Wasm plugin mechanism, implement a plugin that adds Content Security Policy HTTP header based on configuration.
Tech stack
gowasm
Domain
backendsecurity
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoWebAssembly
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60