Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Add feedback Subscribe
Status Shipped
Product DXP Cloud Platform
Categories Infrastructure mgmt.
Created by Guest
Created on Nov 4, 2021

RELATED FEEDBACK

Support for Cloudflare Image Resizing

A lot of solutions we use require and image resizing implementation to improve performance upon our sites.


These solutions require installing third-party plugins and updating image urls with querystring parameters. The resizing of these images happens within the app service.


Cloudflare Image Resizing is a simialr piece of technology however it would perform the resizing upon the cloudflare edge platform.


Would it therefore be possible to support the Cloudflare Image Resizing feature as part of the DXP Cloud Services?


Thanks


  • Post comment
  • Guest
    Reply
    |     Feb 28, 2024

    Exciting that this has been marked as Shipped! Is it possible to get a link to the documentation from Optimizely on how to best implement this feature?

  • Optimizely
    Elias Lundmark
    Reply
    |     Jun 15, 2023

    Hi all,

    Because the options for image resizing on .NET Core are less plentiful in comparison to .NET Framework, we have now started a beta for Image Resizing through the CDN for CMS 12 in DXP Cloud Services. Sign up is available here https://www.optimizely.com/beta

  • Guest
    Reply
    |     Feb 8, 2023

    @Elias, I think option 1 would be our preference as the offloading of processing would be ideal, and the change to existing implementations with other image processors seems like it'd be fairly simple to achieve. Is that a correct understanding?

    Additionally, is this a feature that we can currently request to be lit up in Cloudflare, or is there additional cost to using it?

  • Guest
    Reply
    |     Dec 13, 2022

    Life would be so much better if there was support for cloudflare image resizing.

  • Guest
    Reply
    |     Nov 29, 2022

    Please enable Cloudflare Image Resizing. Cloudflare is such a powerful toolbox, so it's a shame we only get this crippled version in DXP.

  • Guest
    Reply
    |     Nov 24, 2022

    I would love the 1st option, "Using a specially-formatted URL determined by the CDN"

    What version/licensing of/for Cloudflare is there in a DXP environment? Is it supporting the image resizing so a partner can implement this on their own?

  • Guest
    Reply
    |     Oct 23, 2022

    +1 for this one. We really need to have a way of reizing image within the services from optimizely that is not relying on third party tools/licenses but is included within DXP.

  • Guest
    Reply
    |     Sep 9, 2022

    This would be a super useful tool for us, I hope you can implement this in DXP! We are already using query parameters for our image resizing tools, so it would be an easy switch to implement Cloudflare style parameters instead.

  • Guest
    Reply
    |     Feb 8, 2022

    I'm sure you can find a good convention and possibly some basic PaaS-portal configuration to get a good mix of locked down sizing steps and ease-of-use.

  • Optimizely
    Elias Lundmark
    Reply
    |     Nov 24, 2021

    Thanks for sharing this feedback! Image Resizing at the edge is indeed a powerful tool to offload the origin from a very CPU intensive task. Though it may be difficult for us to get away from the query string parameters as this is the CDNs main way of determining resize parameters. There's two ways of deploying the image resizer,

    1. Using a specially-formatted URL determined by the CDN

    2. Using a Worker to extract resize parameters from query string

    Option #1 has the advantage of not requiring a third-party plugin, and option #2 has the advantage of allowing the use of third-party plugins to administrate image resizing but the actual resizing will happen at the edge rather than the origin.

    Would love to hear what direction you'd prefer!