stpp2
stpp2
> The only reason why this PR isn't merged yet is that I'm not sure whether using this package still makes sense given the state of `@angular/ssr` (and how it...
@darkweak thank you so much for the reply! It's a little non-standard, but basically just pass through a new header for any req/res that goes between Caddy and the cache...
Hi @francislavoie, Thanks for jumping in! Basically just like you are able to set custom headers to the upstream/downstream servers with Caddy on specific routes - I was wondering if...
Oh, that's a very valid point with Redis and HTTP. I suppose the `only include a response header to the client when it was cached` is indeed what I'm after....
When it's stored, ideally.
Hmm I haven't thought of using the stored directive, I'll explore that soon - thanks! The use case for adding custom headers here is to use those headers to sync...
I've hit some other blockers with the redis cluster implementation and I've found a way to replicate writes/purges via the headers. Either way I'll try to move forward with adding...
Quick followup @darkweak / @francislavoie - Not sure if this is a core Caddy thing or a Cache-Handler issue, but I can't seem to match anything in the Cache-Status header?...
Oh, really sorry for missing the header matcher! (updated the message above.. fwiw I did use the header matcher type when testing, just a typo in here) And also tried...
Ah, yes! That was it. Setting the directive globally to `order cache after intercept` got it working. (not sure if that has any side effects but will check) Thanks for...