core
core copied to clipboard
Add Souin as available provider to the existing system
| Q | A |
|---|---|
| Branch? | main |
| Tickets | #4512 |
| License | MIT |
| Doc PR | api-platform/docs#... |
Add Souin as an available purger provider instead of the Varnish one to be able to use natively Souin as a cache system inside the Caddy reverse-proxy and refactor the AddTagsListener to be able to customise the HTTP header tag and the separator instead of the forced Cache-Tag from Cloudflare.
note that the ci is broken we're trying to fix underlying issues
@soyuka @dunglas this PR is ready for review
The tests on the main branch break the PHPUnit ones on PRs. Due to the bb2180f0acc091ce62b414bbc80d76971b300e0c commit.
ping @dunglas to review as we discussed with @soyuka
@soyuka I reverted the Cache-Tag into Cache-Tags. Can you re-review for the last time? Ty
Hi there, what about this?
Hey, is there a Chance this feature will be in 2.7 ?
I don't think because they never answered 🙃
@soyuka @dunglas Can I have a review please ? Everything is working as expected with tests. It would be a great add-on on the v3 to deal with the caddy native HTTP cache system.
We're focus on releasing API Platform 3 (which is in beta). We'll review this PR as well as other new features when API Platform 3 will be tagged.
Ready to review/merge.
ping @dunglas @soyuka
Can I have a last review please?
Nice! A few comments lefts but we're almost good to merge imo! Thanks @darkweak sorry for the delays!
@soyuka note this discussion: https://github.com/darkweak/souin/issues/277#issuecomment-1327339148
It seems Souin will start passing any request as soon as the Authorization header (or Cookie) is present in the request, it doesn't provide (nor plans to provide) any sort of "user context"-like feature FOS HTTP Cache bundle, which IIRC APIP relied on before.
Ready for the merge @soyuka
@soyuka note this discussion: darkweak/souin#277 (comment)
It seems Souin will start passing any request as soon as the Authorization header (or Cookie) is present in the request, it doesn't provide (nor plans to provide) any sort of "user context"-like feature FOS HTTP Cache bundle, which IIRC APIP relied on before.
Well, then there is no reason that souin should be integrated into APP.
offtopic:
@darkweak would like to consider changing the souin logic?
Thanks!
@divine note this PR https://github.com/darkweak/souin/pull/283
Anyway, TBH the api platform team won't merge this PR I guess.
merci @darkweak
I cherry-picked it in my PR just to be a bit less provider specific. souin will have native support from API Platform 3.1 (coming out mid-January) you can try it using dev-main for now.