darkweak
darkweak
@long2ice same question then, do you have some logs about that? Are there any error logs during startup? Can you give me more context?
> For who have same problem, I finally use https://github.com/sillygod/cdp-cache That's not a suitable solution because the module you are mentioning is not maintained and doesn't implement fully the RFC....
Hey @daflyinbed maybe that's related to https://github.com/darkweak/souin/issues/523 (on the development repository).
Hey there, @girlbossceo you can just use the following `--with` to build your caddy instance instead of using the `cache-handler` while waiting for the next release on the `cache-handler` repository....
Hey @DzigaV afaik thats not possible. The request coalescing will request once your upstream for a given key, so if your generated keys are equal, it should return the same...
I'm wondering if the coalescing system will send only one request to the backend if an authenticated user and an anonymous user try to send the request on the same...
I'm getting it, **BUT** - if your backend returns a `Cache-Control: no-cache`, it won't be cacheable so each request must have to fetch the origin server. - if your backend...
@DzigaV can you try with `xcaddy build --with github.com/darkweak/souin/plugins/caddy@46601ccfb6a445669bfad6665c5139c671b962d0 --with github.com/darkweak/souin@46601ccfb6a445669bfad6665c5139c671b962d0` and tell me if that is working as expected please?
Hello @daflyinbed thank you for your feedback, I'm investigating on this issue.
`403` Status-code must not be stored.