Cache-control on login page with redirect

  • Resolved MadMonkey

    (@bash2day)


    4 years, 11 months ago

    Hi,

    Hummingbird has been doing a great job for me lately. Thank you. However, there is one issue that I’m facing related to cache-control.

    I’ve got a login page with Nextend social login (Facebook and Google). The idea is that after a successful social login, the page should get redirected to a “user-logged-in” version. What happens instead is the page reloads in user-not-logged-in mode again.

    Nextend advised it has something to do with cache-control and indeed, the cache-control header on login page says max life of 3200. And yet, in Hummingbird I’ve listed the login page as no-cache page in the settings.

    Any ideas what I can do?

    Thanx and greetings

    Jan

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Williams – WPMU DEV Support

    (@wpmudev-support8)

    Hi @bash2day

    I hope you’re well today!

    The cache-control header that you’re referring to would be related to browser caching and the exception that you added would be page caching. These are two different thing. Page Cache is a cache that works entirely server-side. Simply speaking – plugin is generating “static” versions of the pages and when a page is requested it makes WP serve such “ready to use” static HTML file instead of generating it dynamically, as it would happen without it.

    That’s simplified explanation but give the idea. The HTTP headers doesn’t really affect that.

    A browser cache, on the other hand, is cache that’s entirely in user browser. Server sends all the data – regardless whether from page cache or just dynamically generated “on the fly” – the same way as it always does but then browser saves some of that data into cache. When it requests content from site it checks that cache-control header and if that content/asset is not yet expired (according to that lifetime set in header) it simply doesn’t request it but instead reads from local drive.

    These two types of cache are independent, though might affect each other as a page isn’t just a single, simple file but a set of data/assets.

    If you have added exception and that doesn’t help, then see if disabling Page Cache entirely (just for test) helps. If it doesn’t, it would confirm it’s not related to Page Cache.

    In such case try temporarily disabling also Browser Caching (if it’s possible; it not always is) and then check in incognito browser tab (or after clearing browsing data in browser) if it starts to work.

    If yes, that would confirm that it’s a matter of browser caching. Could you, please, test it? We’ll then be able to look for solution/workaround based on results of such test.

    Kind regards,
    Adam

    Plugin Support Dimitris – WPMU DEV Support

    (@wpmudev-support6)

    Hello @bash2day

    I’m marking this topic as “resolved” due to recent inactivity.
    Feel free to post back here any updates or create a new topic about it.
    ??

    Thank you,
    Dimitris

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Cache-control on login page with redirect’ is closed to new replies.