Developer forum

Forum » Templates » Getimage in Dynamicweb 8.5 bug

Getimage in Dynamicweb 8.5 bug

Sten Hougaard
Reply

Hi,

I had hoped that the getimage handler in Dynamicweb 8.5 was fixed so that browsers can start caching images, but no - not fixed yet :-(

Take a look at this "matrix":

The two coloums each show response headers after requesting an image twice. That is: The browser has been there once, requested the image, and is returning to get the image again. The image is not changed. Responding correct to the browser to ensure that the browser will not again download the image (and slow page load down!) involves more http response headers than the Getimage function of Dynamicweb responds with.

Firstly: getimage responds "200 ok" => Yes I have (a new) image, where as the webserver of dr.dk responds: Well, the one you have has not been modified.

Please take som time to fix this bug. It is a major impact on most Dynamicweb soloutions, for instace showing a great number of product pages. It will slow down any soloution using getimage, and looking at it with the positive eyes: It will in a very positive way give free performance improvements to practically any of the websites running Dynamicweb :-)

Thanks!


Med venlig hilsen/Best regards,

Sten Hougaard
Webudvikler

E: sho@1stweb.dk
M: 29850818
A: København/Aarhus . W: www.1stweb.dk
@: netsi1964


Replies

 
Nicolai Høeg Pedersen
Reply
This post has been marked as an answer

Hi Sten

You write GetImage.aspx - are you testing the VERY old .aspx handler or the newer GetImage.ashx handler?

I get 304's from my handler when the images are loaded, see attached.

All the X- headers from dr.dk are just info headers.

The expires header (2019) is a pretty hard one - that image will NEVER be updatable unless you clear browser history. dr.dk can send that, we cannot, because we would have you crying on the phone when you update the image and the customers keeps seeing the old one :-).

We have followed this guideline: https://developers.google.com/speed/docs/insights/LeverageBrowserCaching

Please check again, and give me your URLs you tested and I'll have a look

Nicolai

Capture.JPG
Votes for this answer: 1
 
Sten Hougaard
Reply

I rest my case! Thanks Nicolai! :-)

I get same result now - I am happy, sorry about my false statements in my post... 

/Sten

 
Nicolai Høeg Pedersen
Reply

Så ka' du lære det :-)

 

You must be logged in to post in the forum