Support » Plugin: WP Fastest Cache » compatibility withe EWWW Image Optimizer and ExactDN

  • nosilver4u

    (@nosilver4u)


    The EWWW Image Optimizer has a CDN called ExactDN, and when I try to configure it in WPFC, I get a failure message that says “Bad Request”.
    I’m the developer for EWWW IO, so I know that it’s likely getting a 400 error for trying to access the root of the CDN zone, which is not permitted for security reasons. For example, something like http://test-shanebishop-net.exactdn.com/ will return a 400 error, specifically it will say “Error 0007. We do not process HTML pages.”
    Is there a way to circumvent this auto-verification, and essentially tell the WPFC plugin to use the CDN url as-is?
    Or what would be the best way to address this? I noticed you have a Photon option in the CDN settings, and ExactDN is very similar (implements the same API), or perhaps there is a way for WPFC to automatically get the ExactDN domain?

Viewing 6 replies - 1 through 6 (of 6 total)
  • nosilver4u

    (@nosilver4u)

    Should mention, the last question is not just hypothetical, it actually is possible already with this code:

    if ( class_exists( 'ExactDN' ) ) {
    	global $exactdn;
    	$exactdn_domain = $exactdn->get_exactdn_domain();
    }
    Plugin Author Emre Vona

    (@emrevona)

    I could not understand. isn’t the cdn set via EWWW Image Optimizer? is it set via wp fastest cache cdn panel?

    nosilver4u

    (@nosilver4u)

    The ExactDN domain is auto-configured in EWWW IO, but once our ExactDN code changes the JS/CSS urls, then WP Fastest Cache will no longer attempt to merge/minify any of the JS/CSS files.
    In other plugins, that is typically resolved by configuring the CDN domain/url so that the CDN urls are recognized as “local”, at least in the sense that the files can be found locally and merged as desired.
    Perhaps WPFC wouldn’t do that, but that’s why I was trying to configure the CDN via WPFC also. In other words, the intent of configuring the CDN panel in WPFC was not so that WPFC would rewrite local urls to the CDN, but so that it would minify/combine the JS/CSS files.
    Does that make sense? Is there perhaps another way to inform WPFC what domains can be considered local for minification/combining?

    Plugin Author Emre Vona

    (@emrevona)

    Let me explain what I understood.
    The css/js files are not minified because wpfc recognizes them as 3th part sources, right?

    nosilver4u

    (@nosilver4u)

    Yes, that’s what it looks like. Is there a way to tell WPFC that they aren’t 3rd-party sources?

    Plugin Author Emre Vona

    (@emrevona)

    Can you contact me via email for the solution please: https://www.wpfastestcache.com/contact-us/

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.