• Dear Developer,

    your plugin rocks! thank you for doing such amazing work and sharing it with the community!

    Could I please request a small ability for the “CDN friendly” option to be able change domain for the generated webp images to the CDN?

    Explanation:
    I have an WP Fastest Cache + StackPath CDN integration.

    The way it works (per my understanding) is that all assets links are replaced to my StackPath domain, for example:

    website.com/wp-content/path-to-image.jpg

    becomes:

    [stack-id].stackpathcdn.com/wp-content/path-to-image.jpg

    CDN automatically clones original image from website.com and redistributes a copy from their server locations.

    However, when I use your plugin the new Webp links generated are pointing to the website.com, while it would be great if I could set that new links must using [stack-id].stackpathcdn.com so it will run through CDN route.

    Thank you,
    Max

    • This topic was modified 5 years, 6 months ago by Maximus Light.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author rosell.dk

    (@roselldk)

    Hi Max,

    Thanks for your request.

    CDN plugins actually expect image urls pointing to website. WebP Express simply provides new images and new urls on the website – which is the “origin server”. WebP Express works well with all the CDN plugins I have tested this far, including WP fastest cache.

    If I implement functionality to change the domain, WebP Express will be taking over the job of pointing images to CDN, but only for WebP images. It will still be necessary to have a CDN plugin for pointing other assets. But configuring CDN two places seems like a bad idea. It seems that the functionality is only useful in case there should be incompatibility with a CDN plugin. But I think it is a better route to fix such incompatibilities as they are discovered.

    Do you have the links pointing to your site, but other links, such as css and javascript pointing to stackpathcdn.com ?

    Can you share the website URL?

    Best regards,
    Bj?rn

    Thread Starter Maximus Light

    (@maxshock)

    Morning Rosell,

    thank you for your reply.

    Everything is pointing to correct places for the CDN there is no incompatibilities, except WebP as it points back to ‘origin’ domain because it injects new Webp images after output buffer, while simply changing the origin domain would have CDN’ed the WebP generated images.

    I am very, very sorry that I can’t share the domain as it is confidential at the moment.

    [Sorry for how it sounds:] If you would have a spare moment , you could start StackPath free trial for a month (it doesn’t ask for CC details to have one), then integrate with WP Fastest Cache through CDN tab you would see what I mean.

    Basically all assets becoming stackpath.com/path-to-file.css instead of origin server (Fastest Cache do the same as your plugin, changes the asset links via output buffer), non-asset links ofcourse are staying the same as they should.

    Stackpath automatically mirrors files that are displayed as stackpath.com/path-to-file.css if its referenced from ‘origin server’ so nothing is uploaded/sent to CDN storage specifically.

    Thank you,
    Max

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Feature Request: Ability to set domain for CDN’ is closed to new replies.