We currently eTag / cache resources included in the component repos but do not offer any cache mechanism for resources in /assets. The same mechanism could be applied:
- known assets included in the
index_template are fingerprinted using the same versioning / last_modified logic with version=0.0.0
- assets that are not requested through the
index_template revert to using eTag
We currently eTag / cache resources included in the component repos but do not offer any cache mechanism for resources in
/assets. The same mechanism could be applied:index_templateare fingerprinted using the same versioning / last_modified logic withversion=0.0.0index_templaterevert to using eTag