André R.

+1 , but: > Actually I don't even get how others do deployment without something like this. Manage fine without this making sure params have sensible defaults. A bigger problem...

Yes VCL will have to be adapted for this so recipe is the way to go for that, PHP wise it's specifically: - extension point in hash logic in order...

1) That is about it. Unsure if purging by tag can be done, so might need to keep track of urls to tags using stash for instance. 2) I couldn't...

> you do not want to loose that information, or you won't find your resources anymore. true, good point > 2) ... I'll pass the ball back to the customer...

Small update here, @kmadejski did a small prototype for eZ on this and there are some good news and some bad news: - Tagging is now supported, so it's possible...

> how varnish itself should support the surrogate-control header: varnishcache/varnish-cache#2893 After having read that, I guess it's indeed best to drop the 3 item for now. The main needs are...

Depends on what you mean, but I can't see any mention of Age here: https://www.w3.org/TR/edge-arch/#:~:text=2.2%20Surrogate-Control%20Header But indeed seems this is a known issue when letting reverse proxy cache for long...

> the symfony http-client has been developed ignoring the efforts of PSR-18 I guess they wanted to go beyond what's there, but indeed PSR-18 type hinting would be the way...

You might be underestimating how much more you will have to fix in these parts before it works correctly, the effort to maintain this, and the missed opportunity to integrate...

@hpatoio You ok with doing the fix-ups or would you like us to take over on it?