Skip to content

[RFC] Removing HTTP 1.0 headers #3118

@alexander-schranz

Description

@alexander-schranz
Q A
Bug? no
New Feature? no

Actual Behavior

Actually there are caching headers set for http 1.0 for browser which don't support http 1.1.

Expected Behavior

I would remove them and only set the Cache-Control header for this. I tested some (tools pingdom, yahoo yslow, google pagespeed insight) nobody requires to set the http 1.0 headers anymore.

Steps to Reproduce

Access static files you will get Pragma, Expires and 2x Cache-Control headers.

Possible Solutions

Only set the Cache-Control header here:

'Expires' => '+1 month',
'Pragma' => 'public',

    'Cache-Control' => 'public, immutable, max-age=31536000'

Also we need to update the Vhosts for nginx and apache

Metadata

Metadata

Assignees

Labels

Easy PickRelatively easy to solve for newcomers as wellTechnical DebtImpacts code quality, no or just small impact on end developers and users

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions