Hi Ismail,

Did you also upgrade the web component?

If you are using the latest version of each you should be following the format described here for remote files.

http://imageprocessor.org/imageprocessor-web/imageprocessingmodule/#remote

Drop the protocol and use the relative path only. I think it is the encoding of the protocol part of your path that is causing the problem. You normally wouldn't do that.

Relative parts plus querystring parameters should work fine either encoded or unencoded.

Let me know how you get on.

James

James,

On my local instance i have updated to latest version via nuget which i assume would update all components?  I then tried as per docs removing protocol and replacing ? with / this does not work at all i get errors so i have request like

http://mysite/remote.axd/stormmanagementstaging.blob.core.windows.net/media/19817/feature-02-b-2480-desktop-xl.jpg?anchor=center&mode=crop&width=2480&height=930&rnd=130743523790000000

that gives 

HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  

Please review the following URL and make sure that it is spelled correctly. 

If i do 

http://mysite/remote.axd?http://stormmanagementstaging.blob.core.windows.net/media/19817/feature-02-b-2480-desktop-xl.jpg?anchor=center&mode=crop&width=2480&height=930&rnd=130743523790000000

that works fine

doing 

http://mysite/remote.axd?stormmanagementstaging.blob.core.windows.net/media/19817/feature-02-b-2480-desktop-xl.jpg?anchor=center&mode=crop&width=2480&height=930&rnd=130743523790000000

so removing protocol gives

Invalid URI: The format of the URI could not be determined.

Just to double confirm my umbraco version is 7.2.4

ImageProcessor.dll 2.2.5.0

ImageProcessor.Web.dll 4.1.5.0

You mentioned using relative path only however these images are in azure blog storage.

Regards

Ismail

That's odd. I've just tested the first url on my machine and it works perfectly.

Also, sorry.. I didn't mean relative, I just meant without the protocol.

James,

Still no joy with this.  After upgrade should it have updated my web.config am i missing something do i need to do something in IIS? My url looks like

http://mysite/remote.axd/stormmanagementstaging.blob.core.windows.net/media/19817/feature-02-b-2480-desktop-xl.jpg?anchor=center&mode=crop&width=2480&height=930&rnd=130743523790000000

The image definately exists it looks like its trying to resolve the whole url as opposed to going through to remote.axd and letting imageprocessor do its magic.

Regards

Ismail 

James,

Ok I was using 4.1.5.0 and in your docs the new syntax is for 4.2 upwards.  I upgraded via nuget to 4.3.2 now i get no errors but no image chrome inspector reports 404s old syntax still works.

Regards

Ismail

When i view the url directly in firefox so 

http://mysite/remote.axd/stormmanagementstaging.blob.core.windows.net/media/19817/feature-02-b-2480-desktop-xl.jpg?anchor=center&mode=crop&width=2480&height=930&rnd=130743523790000000

I get

Image cannot be displayed because it contains errors

Regards

Ismail

Derrik,

Make sure your web.config has in configSections

    <sectionGroup name="imageProcessor">
  <section name="security" requirePermission="false" type="ImageProcessor.Web.Configuration.ImageSecuritySection, ImageProcessor.Web" />
  <section name="processing" requirePermission="false" type="ImageProcessor.Web.Configuration.ImageProcessingSection, ImageProcessor.Web" />
  <section name="cache" requirePermission="false" type="ImageProcessor.Web.Configuration.ImageCacheSection, ImageProcessor.Web" />
</sectionGroup>

In httpmodules

<add name="ImageProcessorModule" type="ImageProcessor.Web.HttpModules.ImageProcessingModule, ImageProcessor.Web" />

In modules

 <add name="ImageProcessorModule" type="ImageProcessor.Web.HttpModules.ImageProcessingModule, ImageProcessor.Web" />

and

  <imageProcessor>
<security configSource="config\imageprocessor\security.config" />
<cache configSource="config\imageprocessor\cache.config" />
<processing configSource="config\imageprocessor\processing.config" />

From what I remember after nuget upgrade i had lost modules bit in my web.config

Regards

Ismial

Ismail,

I updated ImageProcessor, ImageProcessor.Web and ImageProcessor.Web.Config through package manager and had to do a little bit of cleanup in the web.config, but I finally got it all working. Thanks for pointing me in the right direction.

Good man Ismail!

Yeah, Nuget has traditionally had a little trouble with configuration updates. It's always best to compare with the configuration specified in the documentation.

http://imageprocessor.org/imageprocessor-web/configuration/

Glad you got it sorted Derrik.

I found remote images not working after installing PostProcessor. Nuget moved my whitelisted Url from RemoteImageService to LocalFileImageService in security.config.

I could have fixed this a lot quicker if it has resulted in an unauthorised error instead of 404.

I hope this saves time for anyone else who encounters this issue. t

is working on a reply...