Cookies caching story

  • Resolved tabasko

    (@tabasko)


    1 month, 3 weeks ago

    Hi dear support,

    I’m using a plugin that sends me a countdown when there are limited-time offers.
    The plugin uses cookies in the following form getUtilizedTime_ditp_countdown_timer_X (X= from 0 to 5)

    Here is from inspector : https://prnt.sc/FGwgmF87wayA

    I’ve added the exclusions in my settings : https://prnt.sc/1Ca6jlvzUTcs
    but it doesn’t seem to be taken into account.

    When my timer expires, my page in the cache is reloaded in an infinite loop ! It’s conceivable that my pugin, when the timer expires, reloads the page, but that’s not the root cause of my problem.
    For the time being I’ve arranged for the evergreen timer to expire at midnight and I’ve programmed a cron that prunes the cache at 00:01. But it’s still a huge problem for me.

    The only way to solve the infinite loop is to purge the cache.
    As soon as the cache is manually purged, everything works perfectly again.

    I don’t know what to do to move forward, or even better assess the situation.

    I don’t want to share my url here, but here’s my Report number: PJXLEHYX

    • This topic was modified 1 month, 3 weeks ago by tabasko.
Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support qtwrk

    (@qtwrk)

    it’s because your site is running on Apache + LiteSpeed ADC

    the issue here is that , the plugin generated cache rule in .htaccess, doesn’t get sync’ed into the ADC setting , so it is not applying

    Thread Starter tabasko

    (@tabasko)

    Can you elaborate a little?
    In your sentence “the plugin generated cache rule in .htaccess, doesn’t get sync’ed into the ADC setting”, by “ADC setting” you mean what exactly? is it WP/plugin side or really server side?

    Plugin Support qtwrk

    (@qtwrk)

    your provider is using set up as Apache as main webserver, then with LiteSpeed ADC as reverse proxy to Apache with caching feature

    in this case , such rewrite rule needs to be put into ADC side as well in order to work properly.

    Thread Starter tabasko

    (@tabasko)

    Here is my HOST support answer :

    The litespeed server is well configured on the server, so other users of the server can use it correctly at the moment.
    However, the LScache service is independent on each hosting, so your configuration will not be the same as that of another user, potentially.

    If you have a particular configuration to set up, you can do so from the .htaccess file on your space, but it won’t be possible to modify the apache configuration for this on the server side in a shared hosting context.

    Plugin Support qtwrk

    (@qtwrk)

    let me explain it this way

    you have ADC + Apache , where ADC is doing cache , while Apache is doing PHP process

    as: Browser <—> ADC (cache proxy) <—> Apache (backend PHP)

    so , ADC is doing the cache by default configuration , now you have some kind of custom cache policy , let’s say , exclude that cookie you mentioned , then how would you expect ADC to follow your cache policy , if you don’t configure it to do so beyond the default configuration ?

    Thread Starter tabasko

    (@tabasko)

    Here is what the plugin support answered :

    I asked my developer to clarify more. He confirmed this issue stems from LiteSpeed, as managing the cache is their responsibility, not ours. I’ve attempted to handle the cache on our end, but due to their advanced caching mechanisms, it has been challenging to override their conditions effectively. We would be very open to hearing what their support suggests.

    information about the product : https://www.peeayecreative.com/product/divi-timer-pro/

    Plugin Support qtwrk

    (@qtwrk)

    the issue is not from plugin dev , but how your hosting provider configure the ADC

    as I have explained , the ADC acts as reverse proxy server with caching , if you have some cache rule with cookie , such rule must be sync’ed into the ADC server, otherwise it will NOT know what to act when such cookie present and proceed in default behavior

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.