[Michael]

Hi,

Currently trying to setup W3TC to use BunnyCDN with FSD, however looking at Bunny’s API docs it looks like the request method for the BunnyCdn_Api class is using the GET method instead of POST for the purge endpoint.
Bunny’s API docs stipulates it should be a POST for that endpoint: https://docs.bunny.net/reference/purgepublic_indexpost
Your code is using wp_remote_get to make the request, and when I try to purge a url, it throws a 405 – disallowed method error.
Perhaps the Bunny API has recently changed this?
Please could you give me a timeframe for when this might be fixed as we currently can’t purge individual URLs from the CDN?

Many thanks,
Michael

[Marko Vasiljevic]

Hello Michael,

Thank you for reaching out and for bringing this to our attention.

I’ve checked this with the team, and this will be fixed in the upcoming W3 Total Cache release.

Thank you for your patience!

[Michael]

Hi Marko,

Thats great, thanks for getting back to me.

Do you have a rough timescale for when the next release will be?

Many thanks,

Michael

[Marko Vasiljevic]

Hello Michael,

Thank you for your feedback.
This should be fixed in the upclomimg relase
Thanks!

[Michael]

Hi Marko,

I notice you have released the next update (2.8.15), but I don’t see that it has addressed the issue raised above. The ‘purge’ method in the Cdn_BunnyCdn_Api class for individual urls is still sending a ‘GET’ request despite the Bunny API docs listing this endpoint as requiring a ‘POST’. https://docs.bunny.net/reference/purgepublic_indexpost

We are waiting for this update to be able to purge newly updated content from our site automatically without having to login to bunny and enter the URL each time. This is super important for us as the e-commerce store we run relies on up to date stock information.

Please can you let me know when this fix will be made and released?

Thanks,

Michael

[Author]

Posts