Surrogate Provider testing for Cloudflare

[joeblew999]

Hey

This is such a great project .

Really great to see Cloudflare as a surrogate provider , since I plan to start using CF to take the load off my Origin servers that run caddy .

I was looking at :
https://github.com/darkweak/souin/tree/master/pkg/surrogate/providers

At the moment it seems handle cache purging, like described here:

https://developers.cloudflare.com/cache/how-to/purge-cache/

https://blog.cloudflare.com/instant-purge/

Apparently they made their enterprise cache purging available to all plans, and expect to begin offering additional purge capabilities to all plan types in early 2025.

--.

Does this help me to set cache headers for Cloudflare ?

"cf-cache-status " is the main header I think that controls caching for CF .

I noticed that the tests are commented out so I am wondering if there is a reason ?

First thing I can think of is that to test this we need a tofu / terraform that sets Cloudflare , so that test can work ?

https://github.com/cloudflare/terraform-provider-cloudflare

Then I was thinking a Domain and web page is needed to help us easily see the results from the browsers side too to help with debugging .

Please let me know your thoughts .

I also use golang to run workers as WASM on Cloudflare workers , which also can leverage caching of course too .

https://github.com/syumai/workers

So there maybe some relationship to this for testing too .