Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This section describes the new dfsmedia pipeline and its capabilities. For a description of the old media pipeline, see this link section 5.2.

Understanding the request

...

The default location is in the website root under App_Data/DigizuiteMediaCache/.

Files are cached based on the request made to the asset. An example request could be: http(s)://<sitecore url>/dfsmedia/29a605d46a3340418c16542f7272c3ec/110-50035

...

ParametertypeDescription
ResultPathstringPath to the directory in which the asset is cached
FileNamestringName of the cached asset
CachedboolBoolean to indicate whether the asset is cached
ResultStreamTask<Stream>Handle for the result stream used to get the asset from Digizuite
ResizeBytesbyte[]If the image is resized and/or compressed, this array contains the result bytes
DownloadUrlstringRedirect url for download requests
StopPipelineboolIf the pipeline should be aborted, for instance due to security violation, then this is true
AssetAssetIndexableAsset model from the index
StatusCodeHttpStatusCodeStatus code used to indicate the request status.

Changing the url

If the new "dfsmedia" pipeline is used, it is possible to use another prefix for the media url. An example could be that one wanted the company name instead of dfsmedia as the media url prefix. This can be done doing the following:

  1. Change setting: DFS.MediaPipeline to new prefix (e.g. company name) in config file DFS.Settings.config
  2. Change path in httphandler section in web.config (See link, section 3.1) to be the new prefix
  3. Change trigger in customHandlers section in DFS.Services.config to be the new prefix
  4. Resynchronize the silo

Doing this ensures the following URL scheme: http(s)://<sitecore url>/<new prefix>/29a605d46a3340418c16542f7272c3ec/110-50035

Manually deleting cache entries

The cache is invalidating if the image in Digizuite is re-transcoded. The cache invalidation results in all the entries for the given asset, being deleted. If one wishes to manually clear the cache this is also an option. There are two ways in which this can be accomplished:

  • Manually deleting the folder in the cache (i.e. delete the folder that has the assetid of the asset that should be deleted).
  • Call the following endpoint in Sitecore: http(s)://<sitecore url>/damforsitecore/mediacache/assetactions/<assetid>, which will also delete the cacheentry for the given assetid.