• Resolved zwaan29

    (@zwaan29)


    Dear support,

    First of all: thank you for developing this great plugin for free. We’ve been testing it on our staging server and all works well, except:

    1. We do have a Litespeed server with LS caching enabled (we prefer to keep using the LS caching module). When we activate WP CF Super Cache together with CF integration, everything works fine. But when users log in to our website, the parameter is being added as expected, but when they click on a link to our website (for example from their email), they are being logged out (just in a normal browser as Chrome).

    Caching mechanism is working — (hit response); but somehow my users get logged out out of a sudden. Would someone be able to have a look at this, please?

    Thanks in advance.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Contributor iSaumya

    (@isaumya)

    Hi,
    when people are clicking on the link from their email or things that link doesn’t have the query string attached and that’s why they are seeing the non-loggedin version.

    In this case, I would suggest you to use the worker mode of the plugin as it should resolve your problem. Also if you are using LS cache with this plugin make sure that you DO NOT turn on fallback cache in this plugin.

    Thread Starter zwaan29

    (@zwaan29)

    Thank you – this is working indeed.

    When I activate the workers mode – it looks like the swcfpc is removed from all URLs.

    Is that correct?

    Plugin Contributor iSaumya

    (@isaumya)

    When I activate the workers mode – it looks like the swcfpc is removed from all URLs.
    Is that correct?

    – Yes the worker mode does not used the cache buster query parameter. It is only used in the default page rule-based implementation.

    @isaumya

    Also if you are using LS cache with this plugin make sure that you DO NOT turn on fallback cache in this plugin.

    Will it clear cloudflare page cache of a single post while updating the post? I’m using the normal Page rules method with LiteSpeed Cache module.

    Plugin Contributor iSaumya

    (@isaumya)

    Will it clear cloudflare page cache of a single post while updating the post? I’m using the normal Page rules method with LiteSpeed Cache module.

    – Well, it should. Why don’t you try and see?

    Thread Starter zwaan29

    (@zwaan29)

    @isaumya

    Thanks a lot for your message.

    When I activate the CF workers as suggested, it tells me:

    Date: Thu, 21 Apr 2022 11:28:22 GMT
    Content-Type: text/html; charset=UTF-8
    Connection: keep-alive
    CF-Ray: 6ff5c69abef2956d-DUB
    Cache-Control: s-maxage=31536000, max-age=60
    Vary: Accept-Encoding
    CF-Cache-Status: DYNAMIC
    alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400
    x-dns-prefetch-control: on
    x-litespeed-cache: hit
    x-wp-cf-super-cache: cache
    x-wp-cf-super-cache-active: 1
    x-wp-cf-super-cache-cache-control: s-maxage=31536000, max-age=60
    x-wp-cf-super-cache-cookies-bypass: swfpc-feature-not-enabled
    x-wp-cf-super-cache-worker-status: miss
    NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
    Server: cloudflare

    Especially: x-wp-cf-super-cache-worker-status: miss

    Can you please guide me on how to make this work, please?

    Thanks in advance.

    Plugin Contributor iSaumya

    (@isaumya)

    The first request will be miss as this is the time the CF server request the request for the first time. But the consequent requests will be HIT. Just do a hard refresh of the page and you will see HIT

    Thread Starter zwaan29

    (@zwaan29)

    Thanks, worked 🙂

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Problems with using plugin + Litespeed’ is closed to new replies.