support multiple cache-valid(ity)/proxy_cache_valid directives

Bug #1873116 reported by Paul Collins
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Content Cache Charm
Fix Released
High
Haw Loeung

Bug Description

Currently cache-valid(ity) has to be a single item:

 - cache-valid: 200 1h

or

 - cache-valid: 200 401 1h

which maps to

proxy_cache_valid 200 1h;

or

proxy_cache_valid 200 401 1h;

Ideally we could also supply a list so that, say

 - cache-valid:
   - 200 301 1h
   - 401 15m

would generate

proxy_cache_valid 200 301 1h;
proxy_cache_valid 401 15m;

which seems to be what is needed to get different lifetimes: https://docs.nginx.com/nginx/admin-guide/content-cache/content-caching/#limiting-or-disabling-caching

Related branches

Paul Collins (pjdc)
description: updated
Haw Loeung (hloeung)
Changed in content-cache-charm:
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Haw Loeung (hloeung)
importance: Medium → High
Haw Loeung (hloeung)
Changed in content-cache-charm:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.