Script blocking (text/plain) and LiteSpeed Cache

  • Resolved cloudres

    (@griotta)


    1 week, 6 days ago

    Hello, we are experiencing what seems to be an unusual interaction between Complianz and LiteSpeed Cache.

    When attempting to localize an external Facebook-related resource, we can see that the script is correctly blocked in advance by Complianz. However, we also notice that Complianz changes the script type from text/javascript to text/plain.

    We are concerned that this MIME type modification might interfere with LiteSpeed’s normal behavior, potentially causing it to bypass the resource or preventing it from being properly processed or cached.

    Could you please confirm whether this behavior is expected when Complianz blocks scripts?

    Also, is it possible that this transformation to text/plain could lead to compatibility issues with LiteSpeed Cache in scenarios like this?

    Thank you in advance for your support.

Viewing 1 replies (of 1 total)
  • Plugin Support Antonio Candela

    (@antoiub)

    1 week ago

    Hi @griotta ,

    Thank you for reaching out.

    Yes, this is expected behaviour. When Complianz blocks a script prior to consent, it changes the script type from text/javascript to text/plain , this is intentional and is precisely what prevents the script from being executed by the browser before consent is given.

    That said, as a general note, aggressive caching can sometimes cause issues with this mechanism. When using LiteSpeed Cache, we generally recommend excluding our parameters from the cache configuration to ensure Complianz functions correctly. You can find all the relevant parameters to exclude by following this guide: https://complianz.io/javascript-delay-in-wp-rocket-and-other-caching-and-optimization-plugins/

    I hope this helps.

    Best,
    Antonio

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.