• Resolved Xandro

    (@sudarshankotian)


    Hi, does this plugin adds base64 encoding to the URL’s?

    Please let me know. I want to find out which plugin is adding this. And I want to remove this somehow.

    Is there a way I can find out if this plugin is not adding it!!? then which one is!

    Thanks

Viewing 13 replies - 1 through 13 (of 13 total)
  • serpentdriver

    (@serpentdriver)

    Cache plugin doesn’t add base64 code to URLs. If you encounter something like this, then it is usually caused by insufficient bots that are not able to differentiate between a base64 code and regular sources such as an image.

    Thread Starter Xandro

    (@sudarshankotian)

    Ok, @serpentdriver thank you for the explanation.

    Thread Starter Xandro

    (@sudarshankotian)

    It is actually your plugin, which is adding this.

    I temporarily disabled Litespeed in one of my sub-domains, and saw that Base64 doesn’t encode the files.

    serpentdriver

    (@serpentdriver)

    Yes, base64 code is used for image placeholder, but that code isn’t added to any URL.

    Thread Starter Xandro

    (@sudarshankotian)

    Ok, so my 1st question wasn’t correct maybe, but that’s what I wanted to know which plugin was adding base64 encode to files.

    Thanks.

    Plugin Support qtwrk

    (@qtwrk)

    what kind of URL you talk about ?

    an example will be helpful to understand what you want to know

    Thread Starter Xandro

    (@sudarshankotian)

    NO. @qtwrk my bad.

    It was not about URL, but links within HTML for a page, because of Litespeed it is (base64 code) being added.

    It came up with this discussion related to Analytics!!

    So, is there a way to not add base64 code to links?

    Is this good practice? (to have base64 code)

    Can we remove it? If we do remove, does any difference in speed optimisation?

    Thank you.

    Plugin Support qtwrk

    (@qtwrk)

    it is added by lazyload or Low Quality Image Preview

    if you don’t want base64 , you can disable lazyload, it should effectively remove them all

    it’s literally like a certain type of resources, like image or font , but directly embed into the HTML source code , I don’t think it has anything to do with cookie consent thing ?

    Thread Starter Xandro

    (@sudarshankotian)

    Yes @qtwrk cookie consent has nothing to with it.

    I had some issues with CAOS plugin related file. So, when I asked for help from the plugin dev.. he said to remove base 64 encoding as he was not able to find the Analytics file.

    And when I temporarily disabled LiteSpeed plugin, it showed the analytics related resources. Then I confirmed it was Litespeed, but I did not get this point, how’s that base64 encoding is also applying to other files? other than images!!!

    Plugin Support qtwrk

    (@qtwrk)

    aha , I see , if you enabled JS delay , the inline js will be converted to base64

    Thread Starter Xandro

    (@sudarshankotian)

    OHH!!! Ok. @qtwrk then for CAOS plugin, what should I do to exclude the script? any idea?

    As it is related to Google analytics, differing this script makes no sense. Analytics won’t give the real data!!

    Any help would be appreciated ??

    Thanks anyway.

    Plugin Support qtwrk

    (@qtwrk)

    open the page source code ,with LSCWP disabled or bypassed , find all the inline script , extract piece of code from them ,add into defer JS exclude list, save and purge all

    Thread Starter Xandro

    (@sudarshankotian)

    Ok, thank you.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘base64 encoding’ is closed to new replies.