Incompatibility w/ Protected Pages

  • Resolved Brad Brown

    (@bradbrownmagic)


    6 years, 2 months ago

    I ran into a problem using a protected page. This is the WordPress protected page/post feature where users need to enter a password to view page contents, but they don’t need to be logged in.

    It appears that Litespeed is caching the “enter password” page. So, once the password has been entered, Litespeed still serves the “enter password” page content rather than the version of the page with the actual contents.

    I got it working by excluding the page from caching.

    As far as I can tell, this limitation isn’t documented anywhere, though I could have missed it. Ideally, Litespeed would detect that a page is protected and either not cache it, or do some behind-the-scenes wizardry to cache both versions and serve the appropriate one. If that’s not practical, it would be good to document that protected pages must have caching manually disabled in order to work properly. That would save others from having to figure it out for themselves.

    So, I think I’m OK, but wanted to document this for anyone else who runs into it, and to make sure the Litespeed devs are aware of the issue.

    • This topic was modified 6 years, 2 months ago by Brad Brown.

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support qtwrk

    (@qtwrk)

    Hi,

    May I know , are you running on LiteSpeed enterprise or OpenLiteSpeed?

    Best regards,

    Thread Starter Brad Brown

    (@bradbrownmagic)

    Not sure. My web host, Hawk Host, provides it so, I suspect it’s enterprise, but that’s a guess.

    Here’s some info from the report. (I deleted the specific directory info from the report.) Does that help? If not, let me know how I can get whatever you need

    erver Variables
    SERVER_SOFTWARE = LiteSpeed
    DOCUMENT_ROOT = XXXXX
    X-LSCACHE = on
    LSWCP_TAG_PREFIX = 94e
    WP_SITEURL = NULL
    WP_HOME = NULL
    WP_CONTENT_DIR =
    SHORTINIT = false
    LSCWP_CONTENT_DIR = XXXXX
    LSCWP_CONTENT_FOLDER = wp-content
    LSCWP_DIR = XXXXX
    LITESPEED_TIME_OFFSET = -14400.0
    LITESPEED_SERVER_TYPE = LITESPEED_SERVER_ENT
    LITESPEED_CLI = NULL
    LITESPEED_ALLOWED = true
    LITESPEED_ON = true
    LITESPEED_ON_IN_SETTING = true
    LSCACHE_ADV_CACHE = true

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    Yes, it’s LSWS enterprise.

    Few days ago we’ve tested password-protected page and it was all fine.

    Could you please submit ticket here and we’d like to dig it deeper.

    Best regards,

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Incompatibility w/ Protected Pages’ is closed to new replies.