Membership Cache Configuration

  • Resolved featuremonkey

    (@featuremonkey)


    1 year, 4 months ago

    Suppose you have a membership website that generates 2 types of pages per post:

    1. The page with the membership wall.
    2. The page with the content.

    How do you configure a cache vary for the following purposes?

    1. Serve page 1 to to requests that
      • do not contain authentication headers.
      • fail to authenticate.
    2. Serve page 2 to requests that contain authentication headers and authenticate successfully.

    Furthermore, how can we serve the pages from a CDN such as QUIC.cloud?

    • How to perform authentication from the CDN level (without involving host server)?

    Here are solutions that I can find from https://blog.litespeedtech.com/2017/12/13/wpw-choosing-between-public-cache-private-cache-and-esi. These don’t work for the following reasons:

    • Public Cache works on the public page 1, but not membership pages.
    • Private Cache works for both, but creates cache of page 2 per member which isn’t good.
    • ESI can’t be served without bypassing CDN to host to finish the template.
Viewing 2 replies - 1 through 2 (of 2 total)

  • +1 I have the same problem

    Plugin Support qtwrk

    (@qtwrk)

    you probably can’t , or at least not without some coding to integrate the ESI API

    Private Cache works for both, but creates cache of page 2 per member which isn’t good.

    ideally , when you use ESI , it will generate cache among all login users , and then use ESI block for content that is private, like username display …etc but again , this will require custom code

    how can we serve the pages from a CDN such as QUIC.cloud?

    that’s what QC CDN does , when a page is served , if it’s cacheable , then CDN will cache this page

    How to perform authentication from the CDN level (without involving host server)?

    well, this is NOT possible , CDN is only a reverse proxy server + caching , it does NOT carry any PHP script of your site.

    so back to your original issue , simply enable “cache login user” ought do it , but then it fallback to your not-working-reason-number-2 that requires ESI , but still, you need some custom code for this…

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Membership Cache Configuration’ is closed to new replies.

Tags