• Resolved andyganesh

    (@andyganesh)


    Hi all!

    I have an issue with caching and preloading pages for logged-in users.

    So, my website is visible only for logged-in users (intracorporate) and the only one way to log in is to use corporate google account. In functions.php there is the code, which redirects all unauthorized users to the login page (custom made).

    So, if I turn off this redirection, every caching plugin (including Hummingbird) works great, TTFB reduces to 40 ms (light speed!). When I turn on this redirection, TTFB becomes 2-3 sec (tooooo long) and causes even Connection Timeout error, when too much users try to load the website at the same time (due to heavy request processing in backend).

    Hummingbird allows to cache pages for logged-in users, but it works like this: when User A visit the page for the first time, he have to wait 2-3 seconds. Then, if he reload the same page, it loads immediately (40 ms). But it is cached only for him, so when User B tries to load the same page for the first time, he also have to wait about 2-3 seconds.

    That’s because caching plugin “surf” the pages like unauthorized user, and can see only login page due to redirection.

    As I can understand, there are 2 ways to resolve the issue: 1) force plugin to preload pages somehow, even for logged-in users (by the way, i don’t need individual versions of cached pages for each user. they looks the same for each user), 2) force plugin to deliver cached page to User B, if User A already visited this page (as I said, I don’t need individual versions)

    Thank you in advance!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Nithin – WPMU DEV Support

    (@wpmudevsupport11)

    Hi @andyganesh,

    I’m double-checking the workflow regarding this with our Hummingbird teams attention to see if there is any workaround that could be suggested.

    Will keep you posted once I get further feedback asap.

    Kind Regards,
    Nithin

    Plugin Support Nithin – WPMU DEV Support

    (@wpmudevsupport11)

    Hi @andyganesh,

    We did check with our team and I’m afraid the workflow of preloading cache for logged in users isn’t something we would recommend. Even if the page is the same it would still be cached each time based on login from different users, and it can lead to performance issues and can end up using high resources.

    The current setting for “Include logged in users” should ensure the pages are cached when it’s accessed by the user which would be much better when compared to preloading since is a resource-intensive feature.

    2) force plugin to deliver cached page to User B, if User A already visited this page (as I said, I don’t need individual versions)

    Unfortunately, this would require custom coding and such an action isn’t supported within the plugin side.

    We would recommend finding the core issue and what’s causing the redirect to not work as expected rather than preloading all the logged in pages.

    Kind Regards,
    Nithin

    Plugin Support Patrick – WPMU DEV Support

    (@wpmudevsupport12)

    Hi @andyganesh

    I hope you are doing well and safe!

    We haven’t heard from you in a while, I’ll mark this thread as resolved.

    Feel free to let us know if you have any additional questions or problems.

    Best Regards
    Patrick Freitas

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