Analysing Cache-Busting in Fiori 1.28
Fiori 1.28, if one uses the cache-buster mechanism of the flp as described in
The fiori cachebuster tokens are transported within the FioriLaunchpad.html as
part of the ServerSideConfig.
(Note that this mechanism is distinct in 1.32, here the fine-grained ( = per library, per application) cache-buster tokens are transported as part of the
TargetMappingsRequest (1.30-1.34) or start_up request (1.36+)
The data structure returned contains generic tokens (ui2CacheBusterToken, ui5CacheBusterToken) and a map of
url prefixes to cachebuster tokens for known and indexed applications.
If a path prefix of a resource matches a provided path prefix, the corresponding specific cachebuster token will be used.
If it does not match, a generic cachebuster token will be used. ( typically the cacheBusting.cacheBusterToken ).
For indexed applications, one must schedule report /UI2/APP_INDEX_CALCULATE https://help.sap.com/saphelp_uiaddon10/helpdata/en/c5/e7098474274d3eb7379047ab792f1f/content.htm
The generic token listens to a general timestamp of the BSP.
Only applications and libraries with a proper manifest will participate in the fine-granular token mechanism.
If links are broken in the blog, then please bring it to the notice of the author by posting a comment to the blog, not by creating a Moderator Alert because 99 times out of a 100, we can’t fix it!. In that last case, we can’t fix it as fast as the author, nor do we have the time.
Thanks, Mike (Moderator)