Forum Replies Created

Viewing 15 replies - 151 through 165 (of 221 total)
  • Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hi Damian,

    The cache operates by storing the php output as a static file. The server will not enter php if the page is in the cache, so no hooks will run on those pages.

    As the rewrite rules operate at the server level (before checking the cache), the rules can check the countries without needing to enter php.

    I recommend you try to use a server level Geo IP system because it can improve your server’s performance if you have many requests that need to be redirected. By using the plugin, each of those requests are forced to enter php at least once, then again when redirected.

    I hope this is helpful, let me know if my understanding is still incorrect, or if you are still confused 🙂

    Cheers,
    Kevin

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hi Damian,

    As it looks like you are using geo-ip related functionality, you may need to do something with the rewrite rules.

    RewriteEngine on
    RewriteRule .* – [E=Cache-Control:vary=%{ENV:GEO_COUNTRY}]

    This will add a vary for each country that visits using geoip databases (essentially, marking each country as a different type of user).

    If my answer is incorrect, I think I misunderstood what you mean, so further clarification could be useful.

    Cheers,
    Kevin

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Glad to hear it!

    We do plan to make some changes to the thirdparty integration, but I will make a note to confer with you if we change this hook in any way.

    Cheers,
    Kevin

    Forum: Plugins
    In reply to: [LiteSpeed Cache] Webp
    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hi jarylw,

    Apologies for the late reply. If you are using a different plugin to convert images to the webp format, then it should be possible to replace cache enabler with LiteSpeed Cache with no issues.

    From what I understand, a plugin like Optimus will take care of the conversion, then you may simply add the apache rules here and it should take care of accessing the webp images.

    Kevin

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hi Damian,

    Do you have any specific requirements for the hook? E.g. only when the user is logged in, only when user is visiting admin page, etc.

    For all visitors and pages, we have an action litespeed_cache_detect_thirdparty.

    If it is an ajax request, it will run at the after_setup_theme hook.
    Else if it is an admin page, it will run at the admin_init hook.
    For all other requests, this will run at the wp hook.

    Will this suffice?

    Cheers,
    Kevin

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hello linusgr,

    The max age you are setting through rewrite rules is likely being overridden by the value set in the LiteSpeed Cache for WordPress plugin.

    Try
    1) Login in to your WordPress Admin Dashboard
    2) Navigate to LiteSpeed Cache Settings
    3) Under the General tab, set Default Public Cache TTL to 86400.

    Regards,
    -Michael

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    No worries on the being logged-in part. I know it’s happened to me more times than I’d care to admit 🙂

    As for the 304 response, this should be handled correctly once we add ETAG support for pages being served from cache. (Still planned for 1.5.8 release)

    Regards,
    -Michael

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hello cybmeta,

    The reason you are seeing version 1.0.8.1 after re-enabling through the WHM plugin is mostly intentional. WHM uses a version list to determine what versions are available for use when performing the enable operation. We purposely delay adding the newest version of our cache plugin to the list for a few days to avoid any scenarios where an uncaught bug might be deployed to hundreds of servers using mass enable.

    Once 1.0.9.1 has been added to the versions list you should be able to select it from the WHM plugins “Version Manager” section. For the time being please upgrade through your WordPress Admin Dashboard.

    Our dev responsible for adding in feed caching is not in this week but if you can describe your issue I might be able to look into it myself.

    Regards,
    -Michael

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hello ReziOnline,

    Just wanted to confirm on the issue you are having.

    After enabling Directory Privacy, you are asked for user and pass when trying to view posts? Are you logged in our out during this?

    If i am misunderstanding your question please let me know.

    Regards,
    -Michael

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Good to know. Please do let us know of any updates to your situation. We’re always working on improving the ease of use of the plugin, so your feedback is very important to us.

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Apologies for the double post, but I wanted to clarify something.

    My previous response made the assumption that your site is using the same environment as other sites (shared hosting). If you can control your own server configurations (e.g. you have a VPS license), then you may be able to change the settings yourself. That said, if you have a VPS license, do note that the LSCache feature is an add-on.

    Hope this helps,
    Kevin

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Thanks for that information!

    I suggest talking to Pro ISP’s server admins to enable the cache for your site.

    Here’s the page to link to them. The page will provide instructions on how to set up the environment so that you could use caching on your site.

    If they have any trouble in getting the cache configured correctly, they may contact us directly, we’re more than happy to help!

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    I see. If you don’t see any headers, then it may be a server configuration issue.

    Could you describe your server setup for me?

    Are you using LSWS Enterprise or OpenLiteSpeed? If enterprise, what license are you using?

    Are you hosting your site yourself or through a hosting company? Do you have access to a control panel? For example, cPanel or Plesk

    Thanks,
    Kevin

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Did you inspect the element prior to or after visiting the page? If you visit the page first, the page load will not indicate anything regarding the cache status.

    Another option is through the error log, but that is a little more involved.

    Let me know if you are able to see it if you open the inspector then visit a page. If not, I can provide some instructions on how to test it with the error log.

    Cheers,
    Kevin

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    I have clarification from both sides 🙂

    So the FileETag rule you listed above does work in Enterprise already. However, as I mentioned before, our cache entries aren’t actual files, so that rule did not work for the requests served from cache.

    That said, the thing I mentioned earlier that will be added in 5.1.8 – we will add an option to our configurations that enable admins to select “add ETags to cache entries”. That should take care of your original issue, I think.

    Let me know if this answers your questions!
    Kevin

Viewing 15 replies - 151 through 165 (of 221 total)