Skip to content

Don't force public in Cache-Control header to prevent conflicts with CDN and Authentication #560

@boombatower

Description

@boombatower

Search for duplicate feature request

  • I already searched, and this feature request or improvement is not a duplicate.

Feature scope

Completely new feature

Feature request related to a problem

"public, max-age={}",

Seems like either an option or simply defaulting to not including it would be better. Otherwise, this breaks authorization such as htaccess when passed through a CDN. The CDN caches the pages and no longer requires authorization.

Dropping falls back to effectively the same behavior when no authorization is required. AFAIK the public option is meant to force caching for resources that are known to be public. That seems like a dubious default.

Describe the solution you'd like

Either drop the public bit or flag to enable/disable it.

Describe alternatives you've considered

Override header via reverse proxy, but then have to recreate file type TTL logic.

Build target

All targets

Additional context

No response

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestv2v2 release

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions