How to force Autoptimize to output protocol-relative URL’s

Autoptimize by default uses WordPress’ internal logic to determine if a URL should be HTTP or HTTPS. But in some cases WordPress may not be fully aware it is on HTTPS, or maybe you want part of your site HTTP and another part (cart & checkout?) in HTTPS. Protocol-relative URL’s to the rescue, except Autoptimize does not do those, right?
Well, not by default no. But the following code-snippet uses AO’s API to output protocol-relative URL’s (warning: not tested thoroughly in a production environment, but I’ll happy to assist in case of problems):

function protocollesser($urlIn) {
  return $urlOut;

8 thoughts on “How to force Autoptimize to output protocol-relative URL’s”

    • Exactly, I would prefer same. Why not I’d go with relative method.
      Just, one thing I’d to confirm from you. Are relative URL support on all devices including low end to high end popular browsers? I’m afraid because, I guess may be some bots generates 404, etc..

    • Thanks for confirming. Despite relative URL feature , with curiosity, I tested the above filter to see how it’s work on my blog. I’m shocked, that as I added the code in snippet plugin, completely my AO aggregated CSS & JS disappeared from source code. Any guess? What could be possible reason

  1. Oh sorry, by mistake typed.
    Final: After adding the new snippet – Now relative URL come automatically in both scheme. Great!

  2. Good info, buy you should also make a setting for opimizing css that are server via .php files
    for example
    they are not optimized.. also for js


Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.