I’m working on adding the proxy-cache plugin to routes, and am seeing some unexpected behavior:
a route with a path like this caches fine (with the api_key param explicitly not included)
v4/word.json/.*?api_key=key
a route with a path like this caches fine (with date included as a param, api_key explicitly not included):
v4/wordOfTheDay?date=yyyy-mm-dd&api_key=key
a route like this shows the cache plugin as active when I check routes/routeid/plugins, but returns no cache headers when called (not a Bypass, just no cache headers at all)
v4/word.json/.*/hyphenation?api_key=key
Is there an issue with caching routes that include non-terminal wildcards, and if so, are there any workarounds? I’ve tried including ‘hyphenation’ in the params config, but that doesn’t make a difference (still no cache headers in response).
Any suggestions gratefully received!
Erin