• Resolved Kenan89

    (@kenan89)


    I have a pull based CDN configured using the W3 Total Cache plugin.

    When browsing the blogs page via CDN, the blog posts rendered are linking to the original site and not the CDN.

    Could this be due to a misconfiguration in W3 Total Cache, or is there something additional that I need to do ?


    I enabled the W3 Total Cache debug output so you can see replaced URLs for CDN.

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @kenan89

    Thank you for reaching out and I am happy to help!
    The CDN (Content Delivery Network) is used to upload and serve static files (images, JS, css )from the CDN
    I’ve checked yoru website and all the files are served via cloudsim00-5a74733fa40f0bedb4a0-endpoint.azureedge.net

    So with the CDN you do not serve the HTML from the CDN (That is a Full site delivery CDN) And as I’ve checked, there is no option to serve the entre website from the CDN using Azure.

    I hope this answers your question.

    Thanks!

    Thread Starter Kenan89

    (@kenan89)

    Dear Marko,

    Thank you for your response.

    Our current setup involves a pull-based CDN. This system retrieves content from the original source and stores it for faster delivery.

    However, there’s an issue with how WordPress handles URLs in the blog section. It appears to be using the original domain name when displaying blog posts. For example, check out cloudsim00-5a74733fa40f0bedb4a0-endpoint.azureedge.net/blog/.

    I had assumed that the W3 Total Cache plugin would automatically update all WordPress-generated links, replacing them with CDN URLs instead of the original source URLs. Although W3 Total Cache seems to have updated many URLs to CDN versions (as seen in the page source of the link I provided), the URLs in blog posts are still pointing to the original source. This is not what I expected.

    view-source:https://cloudsim00-5a74733fa40f0bedb4a0-endpoint.azureedge.net/blog/

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @kenan89

    Thank you for your feedback.
    I am not quite sure which URLs you are referring to.
    As I’ve stated in the previous post, all the static resources, like images, JS, and CSS, are served from the CDN URL: https://cloudsim00-5a74733fa40f0bedb4a0-endpoint.azureedge.net/
    If you are referring to the URL of the pages and sub-pages in the /blog/ page like /m2m/ or /uicc/ The W3 Total Cache does not have any effect on those URLs as the W3 Total cache only rewrites the URLs for the static files

    Please share some more information or screenshots so we can specify exactly the issue you are talking about.
    Just to add, if you check the source, the pages under /blog/ pages are specified with href:

    <div class="elementor-post__title">
    <a >UICC</a>
    </div>


    Thread Starter Kenan89

    (@kenan89)

    Thank you, Marko, for your valuable feedback.

    I completely understand your perspective, and I share the same viewpoint.

    I had anticipated that W3 Total Cache would also be able to convert the URLs “/m2m/” and “/uicc/” since they are automatically generated by Elementor. Additionally, these URLs point to the origin of the website, which is the source of data fetched by the CDN. Specifically, “cloudsim-001-sdc.azurewebsites.net” serves as the origin, and given its automatic generation, I had hoped that W3 Total Cache would be capable of intercepting and converting it.

    Nevertheless, I fully comprehend if this functionality is not within the intended scope of the plugin.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @kenan89

    Thank you again for your feedback.
    This is how the CDN works, it serves objects from the CDN and the URL rewrite is only for those objects that are uploaded.

    Thanks!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Blog page not rendering post links to CDN URLs when using Elementor’ is closed to new replies.