GeekInTheNorth / GeekInTheNorth/Stott.Security.Optimizely

Response Headers when Adding should replace a header if it exists already

Open
#360 0 comments 0 reactions 1 assignee View on GitHub

@GeekInTheNorth is already working on this.

Since Jun 1, 2026.

  • #378 by @GeekInTheNorth — merged
bug Complete
Dominant language
C#
Stars
11
Forks
6
No merged PRs in 30d

Description

Affects In-Proc solutions

How to Reproduce:

  • Go to Response Headers
  • Add a new header for "Cache-Control" with a value of "public"
  • Visit a content page

Expected Result:

Cache-Control header should exist once

Actual Result:

Cache-Control header exists twice, once as the header defined by the CMS Administrator and the default no-cache value for content pages.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.