If your urls are generated correctly (eg a crop alias only dictates the width/height and any focalpoint settings you won’t see rmode=“crop” either as that’s the default)
It seems more like imagesharp.web isn’t intercepting the urls and serving the cropped image. So debug wise maybe check all is well there (no image processor dlls left over from v8)
If you CDN is azure blob storage.. check you’ve added, the separate now, imageSharp package?
builder.CreateUmbracoBuilder()
.AddBackOffice()
.AddWebsite()
.AddDeliveryApi()
.AddComposers()
.AddAzureBlobMediaFileSystem() // This configures the required services for Media
.AddAzureBlobImageSharpCache() // This configures the required services for the Image Sharp cache
.Build();
Previously we had two separate /media and /cache folders in Azure, when I attempt to use AddAzureBlobImageSharpCache(“cache”, containerRootPath: “/”) to linkup the old cache we get a “blobContainerName cannot be null” from the Azure SDK. Practically speaking /cache now being in /media/cache is OK for us and I wouldn’t expect that to be the issue as I manually re-uploaded the image I’m testing with so it must be in the new /media/cache.
The URL we get back from _content.GetCropUrl("authorImage", "blogPostImage"); is: