Add cache-control and etag to capabilities request

Description

Will add the following:

The first line will make sure clients following HTTP spec won't cache the capabilities document (newer versions of QGIS are apparently doing it and tripping over newly added layers), while the second will help clients that can perform a HTTP conditional request to avoid reloading (and make GeoServer recompute) the caps document when nothing changes.

The etag is going to be computed as a combination of the last reload/start plus the update sequence, which is modified at any configuration change.

Environment

None

Status

Assignee

Andrea Aime

Reporter

Andrea Aime

Triage

None

Fix versions

Affects versions

None

Priority

Medium
Configure