You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
the image caching in SharePoint does not seem to be well described (or I am not able to find proper resources)...
Is here someone who knows how it works?
My steps should be easy to reproduce:
create a image in library (e.g. Site Assets)
create a page, include "Image" web part and link the image created in previous step
return to the library and override the image file with different image
return to the page - the web part shows the old image for "hours"
It looks the images are stored in browser cache as a blobs - the url in "inspect" is replaced with a format blob://[domain]/[guid]
It is a bit annoying - I was building a solution based on SharePoint pages, using a mix of OOTB and custom web parts. The solution depends on various images (stored in libraries). In my case - user might need to update images => it would be easier to update just the files (keeping the same name) that force users to use different file names (and search for all instances across multiple pages...)
I could use some timestamp for images in my custom web parts, but it would solve just a part of the problem.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
the image caching in SharePoint does not seem to be well described (or I am not able to find proper resources)...
Is here someone who knows how it works?
My steps should be easy to reproduce:
It looks the images are stored in browser cache as a blobs - the url in "inspect" is replaced with a format
blob://[domain]/[guid]
It is a bit annoying - I was building a solution based on SharePoint pages, using a mix of OOTB and custom web parts. The solution depends on various images (stored in libraries). In my case - user might need to update images => it would be easier to update just the files (keeping the same name) that force users to use different file names (and search for all instances across multiple pages...)
I could use some timestamp for images in my custom web parts, but it would solve just a part of the problem.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions