APO problem - conflict with bypass cache on cookie system

[user7897]

Hello Cloudflare Community,

I’m completely new here and hope to find help. Since I’m a new user and can only embed 1 pic but and only 2 links so I have used 1 image and 2 Imgur links to link the other images.

We have a site where we use for branding reason a short preloader. This preloader is using cookies. The problem is now that APO is bypassing the cache. So basically Cloudflare APO is bypassing the cache even when there is an active cookie of the preloader.

Right now the setting of the preloader is “once per session” and the session cookie of the preloader is added after the first visit.

This means that visitors will only get cached content (HIT) on their first visit when they have no preloader cookies set. They will get uncached content (BYPASS) on all subsequent page visits in a session.

Result with preloader: https://imgur.com/a/CDAU7F8
Result without preloader: https://imgur.com/a/3VIUQwq

The result is that the preloader is not working with the activated APO.
Any trick on how to prevent this behavior?

Thank you.

[sdayman]

I do believe cookie control is on the roadmap for APO, so you’d be able to ignore that cookie, but I believe that would be on Business and Enterprise plans:

@yevgen

We are working to support APO integration with Page rules:

• bypass on cookies to support custom cookies (Biz plan)
• cache level bypass to bypass specific pages in APO
• edge caching TTL to shorten default TTL for specific pages in APO

Though @yevgen’s example appears to work in the opposite way as what you want.

[eva2000]

@user7897

Any trick on how to prevent this behavior?

maybe if loftloader could change the cookie for wordpress-loftloader* as wordpress-* might match what APO is looking for to bypass cache https://support.cloudflare.com/hc/en-us/articles/360049822312

[yevgen]

true, we bypass any request with cookies wordpress*. The easiest workaround is to rename cookie.

[user7897]

Thank you all for your quick responses. Really appreciated to see the community effort. Also thx yevgen to confirm officially the behaviour… Will try this solution first and in case there is still something not working I will be back here.