Skip to content

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

Description

@GeekInTheNorth

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.

Metadata

Metadata

Labels

CompleteDescribes an issue where development is complete and this item will be included in a release.bugSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions