shift8

Thanks for using our service!

Currently there is not a way to disable specific elements from being routed through the CDN. As a future feature, based on quite a few asking for this, we are working towards implementing a feature where you can add files/paths for the CDN to “ignore”. Stay tuned for a future plugin update to implement this!

Thanks again

Follow up note :

The issue with not being able to click the test url right away, sometimes it takes up to 5 minutes for a site to propagate throughout our network. I apologize but this delay is difficult to avoid but we will look into ways to speed this up.

Hello!

I’m sorry to hear of the issues that you have outlined here.

I’ll make a note to update our install instructions. The issues complained by webpagetest.org are because they have not classified us as an officially recognized CDN

A similar issue existed with GTMetrix. This was resolved by us contacting them to let them know the hostnames of our CDN so that they could add it to their system to recognize. The issue is these webpage speed testing services dont inherently “know” you are using a CDN. They just put a static list of known CDNs together and recognize the hostname as a CDN, this has no bearing in performance at all just with the score of the particular testing service you are using.

Furthermore, I believe we have already contacted webpagetest.org to add our CDN and it seems like they are not actively maintaining it or simply did not respond. You are welcome to contact them yourself or use something like GTMetrix for your testing.

Thanks!

Going to go ahead and close this issue. Feel free to open a new issue if you want assistance troubleshooting again.

Thanks!

Alright – I am indeed trying to be helpful. I wont ask for any form of access moving forward.

Looking at the server logs on our side wouldn’t be helpful here because whats happening is that the rewrite functionality in our plugin is being interrupted for some static assets (not all) being rewritten.

The functionality of the CDN on our side isn’t what the question is here, rather why only some static assets are being overwritten but not all. The rewrite functionality in our plugin is very similar to how WP Rocket works (For example) so I know best practices are being followed there.

The real issue in my experience (as reported by other users in this forum) is that sometimes another plugin can cause conflicts with rewriting of content in this way, which is my feeling of whats happening here.

I apologize @ipstenu – both @sylvertech and myself are just frustrated about this long standing issue. I’d like to support him as best as I can, even though this is a free service.

Truly something weird. [redacted ask for access]

Something is definitely interfering with the ability to rewrite static assets with our plugin. The code our plugin uses to rewrite is very similar to W3 total cache and WP Rocket among others so there’s nothing special happening under the hood of our plugin.

[removed]

• This reply was modified 5 years, 6 months ago by Ipstenu (Mika Epstein). Reason: removing admin related asks

I had a similar experience with another user where a completely unrelated plugin was actually interfering with our plugin’s ability to rewrite all static assets.

Some plugins can interfere with this process by affecting the filter / action priority or importance. And it can be a random plugin that does something that you would not think to potentially affect how a CDN plugin works.

What we did in that scenario was open the site in one browser with the developer console + network tab open. Then disable one plugin at a time while checking the network tab of your browser to see if the rewrite issue is resolved and all static assets start to rewrite properly to go through the CDN.

Once you have identified the plugin you can then determine if its possible to simply keep it deactivated or find an alternative.

As a last resort, I would say that most of the top tier caching plugins like W3 Total Cache and WP Rocket offer the ability to rewrite assets to go through your CDN of choice. You can always try that method though our CDN plugin works the same way as WP Rocket (for example) so the problem may not just go away, but its worth a shot as a last resort.

I’m not giving up! I think if we just rule out each and every plugin , refresh the network tab and look at those static assets, then once we see all the assets go through the CDN we will know which plugin is causing a problem.

Hello!

An update to our infrastructure was just pushed out that no longer will be setting the cookie in this way. You might have to clear browser cookies in your browser to see yourself but I would hope that the GTMetrix report will no longer complain about this.

Thanks!