• Resolved anheco

    (@anheco)


    Hi,

    I’m using the plugin on a non LSWS.

    Yesterday I gave a try to the cdn feature and plugged my domain’s “A” zone to the IP associated to the domain I was attributed.

    I’m unsure about the use of the “bypass cdn” feature in the quic.cloud dashboard though.

    I checked, and cleared the cache, but all requests to my site are still transiting through QUIC.Cloud IPS and pages are still being cached.

    Is it because I’m pointing my domain instead of using QUIC.Cloud name servers?

    Does this mean quota is still used as long as I don’t manually switch back my “A” zone to the original?

    Thanks for all your clarifications !

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

    (@qtwrk)

    it may take few moments for changes to take effect though , if after long time it still proxy through the CDN, then please provide the report number

    you can get it in toolbox -> report -> click “send to LiteSpeed”

    I will check.

    Thread Starter anheco

    (@anheco)

    I confirm my pages are still being cached although the option for bypasing CDN is still checked

    Report WILMBRUV

    Plugin Support qtwrk

    (@qtwrk)

    I don’t see the CDN header now , do you still see it?

    Thread Starter anheco

    (@anheco)

    Earlier today I changed the “A” setting to my original server instead of the CDN because I couldn’t understand what was going on (Plus the 520 error mentioned in another post was something I couldn’t afford to let happen)

    That’s it for my journey using the quic.cloud caching feature ??

    Plugin Support qtwrk

    (@qtwrk)

    aye , as sorry as it is , for proxy service like CDN, it’s not uncommon that some kind of security feature from origin will interpret it as attack since one or few IPs sends multiple requests and blocks the connection that ends up in 520 error

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘QUIC.cloud CDN Bypassed > Pages still cached’ is closed to new replies.