hasadna/open-bus-map-search

add security headers to our nginx configuration

Open

#939 opened on Nov 21, 2024

View on GitHubContributor guide
 (3 comments) (0 reactions) (1 assignee)TypeScript (125 forks)auto 404
backendcigood first issuelow priority

Repository metrics

Stars
 (95 stars)
PR merge metrics
 (PR metrics pending)

Description

We want to allow communication with the following origins:

  • self
  • google analytics (google-analytics.com, googletagmanager.com)
  • fonts.gstatic.com, fonts.googleapis.com
  • *.hasadna.org.il

Also, feel free to apply more security best practices (iframes and such)

Contributor guide

Research direction
Research common security headers such as Content Security Policy, X Frame Options, X Content Type Options, and configure them in the nginx configuration file.
Tech stack
None
Domain
security
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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
nginxsecurity headers knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70