Sharepoint - Logo bei klick auf "zurück" rotes X

[Bjoern28 10]

Hallo zusammen,

 

wir haben hier ein problem.. Sharepoint rennt hier 1A.. unter

 

Site Settings - Title, Description, and Icon

 

haben wir eine LOGO URL eingetragen.. Logo liegt natürlich direkt auf dem Sharepoint. Das klappt auch alles..

 

Wenn ich nun irgendwohin klicke sehe ich oben Links mein Logo.. klicke ich nun auf den zurück Button im IE sehe ich statt des Logos das rote X

 

Aktualisiere ich die Seite F5 etc.. sehe ich das Logo wieder..

 

klicke ich wieder auf zurück wieder rotes X

 

also irgendwie nervt das.. ich finde aber auch nichts?!

 

Hat da jemand eine Idee?

[Kolabeur 10]

Hallo,

 

schau Dir mal das Thema Blob-Cache des SharePoint an, dazu gibt es auch ein Whitepaper.

 

Hier ein Auszug daraus:

 

Configuring and Managing BLOB Cache:

 

 

•A mentioned earlier BLOB Cache is enabled by IIS site or SharePoint Web Applicatio. All you need to do is go to the web.config and modify the BlobCache node as enabled (Reference). There are several other configurations that are available for tuning the BLOB cache, I recommend reading the whitepaper for those details.

 

•For the application pool you will need to increase the startup and shutdown time limits. It is recommended to set it to 300 seconds which will allow enough time initialize or serialize on startup or shutdown. Note this does not mean it takes 300 seconds to perform the operation, however it prevents IIS from terminating the application until 300 has elapsed so the cache is not lost (great reference).

 

•It is recommended to keep all content to be cached in a specified list and sure the site containing that list is stable. This is because frequent changes to the site or list will invalidate all the cached files.

 

•To flush cache a simple IIS Reset can be performed, the SharePoint API can be used or you can finally disable the cache, delete the folder that contains the cache and then re-enable the cache in the web.cong.

 

In summary use BLOB Cache:

 

 

•If there is a high read to write ratio BLOB caching should be used. For instance you would want to cache a site logo that is used on every page request versus a collaboration word document that is actively updated.

 

•It is optimized for supporting large files which can significantly reduce bandwidth between the WFEs and SQL Server.

 

•It is optimized to support cache control headers so that clients can cache small files which can reduce overall number of hits to the WFEs.

 

•If there is anonymous access, there can be dramatic improvements because permissions do not have to be validated for cache files.

 

•Client applications that use range requests can optimize load times to access large files.

 

Hier findest Du mehr Infos dazu:

 

A Static State: SharePoint 2010 Cache

 

Gruß

hajohanf

[Bjoern28 10]

Super,

 

danke dir :)