Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
schedules-legacy
schedules-legacy
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 17
    • Issues 17
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • SRCT
  • schedules-legacyschedules-legacy
  • Issues
  • #20

Closed
Open
Opened Sep 12, 2016 by Mark Stenglein@mstengleContributor
  • Report abuse
Report abuse

Security hardening for production

http://expressjs.com/en/advanced/best-practice-security.html

Look at that and decide what to do about it when we get to the point where it makes sense.

Assignee
Assign to
2.0 "Lunar Edition"
Milestone
2.0 "Lunar Edition" (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: srct/schedules-legacy#20