Bug #35870: mod_expires is not loaded - Installer - Foreman

Bug #35870

mod_expires is not loaded

Added by Ewoud Kohl van Wijngaarden 4 months ago. Updated about 1 month ago.

Status:

Closed

Priority:

Normal

Assignee:

Ewoud Kohl van Wijngaarden

Category:

Foreman modules

Target version:

Foreman - 3.5.2

Difficulty:

Triaged:

Yes

Bugzilla link:

2160056

Pull request:

https://github.com/theforeman/foreman-installer/pull/829, https://github.com/theforeman/puppet-foreman/pull/1101

Fixed in Releases:

Foreman - 3.5.2, Foreman - 3.6.0

Found in Releases:

Foreman - 3.3.0, Foreman - 3.4.0, Foreman - 3.5.0

Red Hat JIRA:

Description

In #34590 the default modules were no longer loaded, but this also disabled mod_expires. This makes #33956 less effective. It is still an improvement over serving assets via Rails, but it doesn't allow the browser to aggressively cache assets.

It should be noted that mod_expires in puppetlabs-apache is a bit special. I ran into this in https://github.com/puppetlabs/puppetlabs-apache/pull/2288, so the fix may be needed in multiple places.

Associated revisions

Revision a132b682 (diff)
Added by Ewoud Kohl van Wijngaarden 3 months ago

Fixes #35870 - Ensure mod_expires is loaded

In case only minimal Apache modules are loaded then mod_expires may not
be present. The result is that assets are sent without headers that
allow browsers to cache it.