Hi Alex,

Did you install ImageProcessor module for Azure version in your local machine, right? So did you config blob storage provider and connection string for the default blob provider? You can see what needed configuration for Azure cache in this current git source for image processor package https://github.com/vnbaaij/ImageProcessor.Web.Episerver/blob/master/src/ImageProcessor.Web.Episerver.Azure/AzureBlobCache.cs

 public AzureBlobCache(string requestPath, string fullPath, string querystring)
            : base(requestPath, fullPath, querystring)
        {
            // Get the name of the configured blob provider
            string providerName = EPiServerFrameworkSection.Instance.Blob.DefaultProvider;


            if (rootContainer == null)
            {
                // Get the name of the connection string from there
                string connectionStringName = EPiServerFrameworkSection.Instance.Blob.Providers[providerName].Parameters["connectionStringName"];

                // Retrieve storage account from connection string.
                CloudStorageAccount cloudCachedStorageAccount = CloudStorageAccount.Parse(ConfigurationManager.ConnectionStrings[connectionStringName].ConnectionString);
                // Create the blob client.
                CloudBlobClient cloudBlobClient = cloudCachedStorageAccount.CreateCloudBlobClient();


                // Retrieve reference to the container. Container is already created as part of the initialization process for the BlobProvider
                rootContainer = cloudBlobClient.GetContainerReference(EPiServerFrameworkSection.Instance.Blob.Providers[providerName].Parameters["container"]);
            }

            //cachedCdnRoot = Settings.ContainsKey("CachedCDNRoot")
            //                         ? Settings["CachedCDNRoot"]
            //                         : rootContainer.Uri.ToString().TrimEnd(rootContainer.Name.ToCharArray());

            if (Settings.ContainsKey("CDNTimeout"))
            {
                int.TryParse(Settings["CDNTimeout"], out int t);
                timeout = t;
            }

            // This setting was added to facilitate streaming of the blob resource directly instead of a redirect. This is beneficial for CDN purposes
            // but caution should be taken if not used with a CDN as it will add quite a bit of overhead to the site.
            // See: https://github.com/JimBobSquarePants/ImageProcessor/issues/161
            streamCachedImage = Settings.ContainsKey("StreamCachedImage") && Settings["StreamCachedImage"].ToLower() == "true";
        }

Hi Alex,

Did you get any further with this? If not, let me know. I'm pretty sure we can get to a working situation.

This code doesn't work..Will be obliged if u provide further code than this too.Regards https://mykfcexperience.website/

Hi Vincent,

I didn't get any further unfortunately. I played around with Binh's code but couldn't get that working either. 

Any advice?

Thanks :) 

Hi All,

I'm back trying to get this to work again, but I've not been able to progress any further.

I've tried make changes to the config files, but it's just guess work. - what changes do I need to make to get this running locally and on a multi-site DXC once we deploy?

The errors are still the same:

2019-10-03 08:20:39,847 [21] ERROR EPiServer.Global: Unhandled exception in ASP.NET
System.NullReferenceException: Object reference not set to an instance of an object.
   at ImageProcessor.Web.Episerver.Azure.AzureBlobCache..ctor(String requestPath, String fullPath, String querystring)
   at lambda_method(Closure , String , String , String )
   at ImageProcessor.Web.Extensions.TypeInitializationExtensions.InstanceCreationFactory`3.CreateInstanceOf(Type type, TArg1 arg1, TArg2 arg2, TArg3 arg3)
   at ImageProcessor.Web.Extensions.TypeInitializationExtensions.GetInstance[TArg1,TArg2,TArg3](Type type, TArg1 argument1, TArg2 argument2, TArg3 argument3)
   at ImageProcessor.Web.HttpModules.ImageProcessingModule.<ProcessImageAsync>d__31.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Web.TaskAsyncHelper.EndTask(IAsyncResult ar)
   at System.Web.HttpApplication.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

There appear to be three services in the security.config - which one do I need for which environment? I presume that I need one configured for my local env and then transform it when we deploy to DXC. is that right?

Kind regards,

Alex

I've managed to get this working locally! Basically by paying more attention to the example configs on Github. So I'm hoping that if I've setup my transforms properly then this will continue to work once we deploy to DXC... we shall see :)

Hi Alex, hopefully you have gotten this to work already but here are few reminders:

• if you are using the ImageProcessor.Web.Episerver, you should have ONLY ONE imageservice in the configuration
  • because the current implementation takes the first imageservice from the configuration (or default which would be null)
    • code: https://github.com/vnbaaij/ImageProcessor.Web.Episerver/blob/master/src/ImageProcessor.Web.Episerver/EpiserverImageProcessingModule.cs
• on local development you should make sure you use the "FileBlobCache" cache which comes with this package
• for Azure/Episerver DXC you would have a configuration transform that switches the "FileBlobCache" to the ImageProcessor.Web.Episerver.Azure packages "AzureBlobCache" cache implementation

If you want to use this package but don't want to store the cached images to the same location with the original image then

• in local development you can used the default DiskCache
• for Azure you can use the package https://www.nuget.org/packages/ImageProcessor.Web.Plugins.AzureBlobCache/
  • in DXC Service I believe you need to ask them to create you a new container (the plugin tries to create the configured container if it doesn't exist but I'm not sure do you have/get the required access keys in DXC)

Hi Antti,

Many thanks for that information. I'm yet to deploy my code to DXC and to therefore test the transformed config, but everything is working locally and is awesome.

I'll definitely have a look at the AzureBlobCache plugin as keeping the produced images cached elsewhere sounds like a nice and clean approach, thank you

Alex

Hi Alex,

Did the plugin work for you? Or did you find another approach for this issue?

Thank you

Salmin

Hi Salmin,

I've yet to look into the AzureBlobCache plugin, but ImageProcessor itself is running on our live site and we're very happy with it!

Alex

Our problem might not be the same as yours, but maybe you have came across it since your solution is working on DXC.

Our codebase works fine locally and on integration, but when deploying to preproduction we get errors with loading images through the ImageProcessor:

Removing the query-params will make the image load instantly, but having them on gives errors and this is the result (se image):

What got it working for me was understanding how the config files worked for local vs production and applying the right config for the right environment.

Can you share your config files? Although I didn't have to touch processing.config - i did need to strip out the unwanted config from cache.config and security.config

Hi,

Thank you for your time. Here's are config

https://pastebin.com/iGn3F62t

The log stream says:

2020-03-02T14:34:20,Error,1bcccf,637187564609804321,0,12632,351,"EPiServer.Global : Unhandled exception in ASP.NET
System.Web.HttpException (0x80004005): Server cannot append header after HTTP headers have been sent.
   at System.Web.HttpResponse.AppendHeader(String name, String value)
   at ImageProcessor.Web.HttpModules.ImageProcessingModule.SetHeaders(HttpContext context, String responseType, String[] dependencyPaths, Int32 maxDays, Nullable`1 statusCode)
   at ImageProcessor.Web.HttpModules.ImageProcessingModule.SetHeaders(HttpContext context, Int32 maxDays)
   at ImageProcessor.Web.HttpModules.ImageProcessingModule.PostReleaseRequestState(Object sender, EventArgs e)
   at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.<>c__DisplayClass285_0.b__0()
   at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)",

Can you share your cache.config and security.config files as well?

This thread suggests a setting in the security.config as a potential culprit.

Here they are:

<imageProcessor>
<security>
<services>
<service name="EpiserverImageService" type="ImageProcessor.Web.Episerver.ImageService, ImageProcessor.Web.Episerver">
<settings>
<setting key="OnAzure" value="true"/>
</settings>
</service>
</services>
</security>
<caching currentCache="EpiserverAzureBlobCache">
<caches>
<cache name="EpiserverAzureBlobCache" type="ImageProcessor.Web.Episerver.Azure.AzureBlobCache, ImageProcessor.Web.Episerver.Azure" maxDays="365">
<settings>
<setting key="StreamCachedImage" value="true"/>
<setting key="CDNTimeout" value="1000"/>
</settings>
</cache>
</caches>
</caching>
<processing configSource="config\imageprocessor\processing.config"/>
</imageProcessor>

As you can se, we have added: <setting key="OnAzure" value="true"/>

I just noticed that our primary domain was set to *

So I tried switching it to the preprod domain, fixed the issue!