Kenan89

Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • 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.

    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/

Viewing 2 replies - 1 through 2 (of 2 total)