quic.cloud and ESI

  • Resolved Nic Windley

    (@nisiwi)


    3 years, 10 months ago

    Hello Litespeed Team,

    I’d like some advice on the correct configuration to ensure LiteSpeed and quic.cloud are configured optimally when using ESI.

    If I configure quic.cloud to only cache static pages all requests are served from LS Cache and ESI works. Even though ESI is only being used on a few pages.

    If I include dynamic pages then requests are served from QC cache (once primed), however, ESI does not appear to be supported as it creates a static version of the dynamic page.

    Have I observed this correctly? Is there a way to have only the ESI part served from LS cache and the rest from quic.cloud when using ESI?

    • This topic was modified 3 years, 10 months ago by Nic Windley.
Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support qtwrk

    (@qtwrk)

    3 years, 10 months ago

    Hi,

    May I know how did you test the ESI ?

    I just used a widget as example which with QC dynamic cache enabled , it worked as expected.

    Best regards,

    Thread Starter Nic Windley

    (@nisiwi)

    3 years, 10 months ago

    Thanks for responding qtwrk.

    I have a page with a form block using ESI that had re-captcha which if it gets cached receives spam as re-captcha won’t work correctly.

    When using quic cloud with dynamic cache enabled I seem to get spam. When I don’t use dynamic cache I don’t get spam.

    Thread Starter Nic Windley

    (@nisiwi)

    3 years, 10 months ago

    From your initial response qtwrk caching dynamic pages in quic.cloud and using LS ESI should work.

    I realise my observation may not be conclusive so is there a method I can use to test the ESI block is not coming from the public cache ?

    I will re-enable quic.cloud dynamic caching for now and continue to monitor.

    • This reply was modified 3 years, 10 months ago by Nic Windley.
    • This reply was modified 3 years, 10 months ago by Nic Windley.
    Thread Starter Nic Windley

    (@nisiwi)

    3 years, 10 months ago

    Aha, it looks like a config problem (my fault). The form was set to private cache which also included the reCaptcha element. I’m going to split out the reCaptcha and diable caching for that completely.

    Is it possible to use the ReCaptcha mechanism in quic.cloud to prevent form spam, in the same way as you can with cloudflare ? i.e. you offload the script to the CDN ?

    Plugin Support qtwrk

    (@qtwrk)

    3 years, 10 months ago

    Hi,

    The QC itself has recaptcha protection already

    and if you are using recaptcha from your plugin , it should work as it without CDN.

    Best regards,

    Thread Starter Nic Windley

    (@nisiwi)

    3 years, 10 months ago

    Ok, so would QC reCaptcha also protect the form from spam (like Cloudflare) ? Or do I still need reCaptcha on the form ?

    If not currently supported, could QC also protect forms from spam in future ?

    Plugin Support qtwrk

    (@qtwrk)

    3 years, 10 months ago

    Hi,

    It’s kind of like Cloudflare’s captcha challenge

    Best regards,

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘quic.cloud and ESI’ is closed to new replies.