URLs in ImageVault 3.4
In order to increase security and make ImageVault work better with search engines and other applications we have made some changes to the way we handle the URL's.
Both the new and the old version are based on a HttpHandler. This allows us to check access rights, make conversions and finally deliver the requested image.
The first change regard the way that the URL is formatted. The new version of the handler requires that the server is using IIS 7.0 or later, hence we can map any URL to the handler. In earlier version IIS used script maps to map file extensions to be executed by ASP.NET. A workaround to that problem was to map the handler to the name ImageVaultHandler.aspx. Since .aspx pages was already mapped to ASP.NET we could get the call thru to our own handler.
A typical URL could look like this.
http://localhost/ImageVault/Images/width_122/conversionFormatType_Jpeg/id_14/ImageVaultHandler.aspx
But since we now can map any URL to ASP.NET we can make the URL appear to be an image that is served directly by the IIS.
http://localhost/ImageVaultFiles/id_8/cf_45/TestImage.jpg
In this case we have mapped the handler against “ImageVaultFiles/*” instead.
Another change is that in the previous version it was also possible to change the URL and have the image converted to the requested format. This is not longer possible, unless the actual format has already been published. When using the API on the server side to create the URL to the image, only that specific format is marked as approved for publishing.
Skriv kommentar
Kategorier
- SharePoint 2 inlägg
- ImageVault 18 inlägg
- EPiServer 19 inlägg
- ProcessMap 2 inlägg
- EmailEncoder 1 inlägg
Arkiv
- mars 2010 2 inlägg
- april 2010 1 inlägg
- maj 2010 1 inlägg
- juni 2010 1 inlägg
- januari 2011 4 inlägg
- februari 2011 1 inlägg
- mars 2011 1 inlägg
- maj 2011 2 inlägg
- juli 2011 3 inlägg
- augusti 2011 1 inlägg
- september 2011 1 inlägg
- januari 2012 2 inlägg
- mars 2012 1 inlägg
Diskussion
Menno, den 26 augusti 2010
It seems that I have both handlers on my web site. I upgraded from episerver 5 to 6 and then installed imagevault. Can I now remove the old handler? And does the new handler need execute permission ?
Johan, den 13 september 2010
Yes you can remove the old handler. It is not removed by the installation program, since there could be implementations that manually create urls in the old format. Please clarify the question about execute permissions?