LiteSpeed Cache bypass with text/plain scripts

  • cloudres

    (@griotta)


    1 month, 3 weeks ago

    Hello, we are currently investigating a potential compatibility issue between LiteSpeed Cache and third-party script blocking mechanisms (specifically Complianz).

    When a Facebook-related external script is blocked by Complianz, its type is changed from text/javascript to text/plain.

    This is expected on their side for consent management purposes.

    However, we are observing that, in this scenario, LiteSpeed seems to bypass or not properly process/cache this resource.

    Could you please confirm whether LiteSpeed Cache ignores or skips scripts when their MIME type is changed to text/plain? Could this behavior result in a cache bypass or prevent proper optimization/localization?

    Additionally, we would like to ask a related question: when a resource is localized (for example, an external JS hosted locally), is there a way to define a specific cache expiration (TTL) for that localized file within LiteSpeed Cache?

    Understanding this would help us better control caching behavior for third-party scripts.

    Thank you in advance for your support.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support litetim

    (@litetim)

    1 month, 3 weeks ago

    @griotta to give you a better response, please create a report, from LSC => Toolbox => Report => click on “Send to Litespeed”.
    Share the ID generated and we can help you.

    Thank you

    Thread Starter cloudres

    (@griotta)

    1 month, 3 weeks ago

    @litetim ZLHCKWQF

    Plugin Support litetim

    (@litetim)

    1 month, 3 weeks ago

    @griotta Thank you for report.
    Litespeed will run first on the page source: minifying, gathering all JS.
    Then comes Complianz adding text/plain to all scripts.
    LSC will process all JS <script> tags. But will ignore script added in Exclusion settings.
    What is the end result you are looking to achieve?

    Localisations do not have a TTL and, because of a bug, you have to manually delete localised resources( wp-content/litespeed/localres ). The bug is know and we are going to address it.

    Thread Starter cloudres

    (@griotta)

    1 month, 3 weeks ago

    What is the end result you are looking to achieve?

    What we would like is for all external resources that can be charged to the Facebook for WooCommerce plugin to be localized, but with a fairly fast TTL. This isn’t currently the case with the configuration I’ve shown you.

    Localisations do not have a TTL and, because of a bug, you have to manually delete localised resources( wp-content/litespeed/localres ). The bug is know and we are going to address it.

    🙌🏼

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.