Re-enable static web assets caching

[exalate-issue-sync]

There has been caching in place for static web assets for a few weeks. It was not stable. Needs investigation so that it can be re-enabled reliably.

The idea was to set the last modification date of assets to the most recent service start time, since we can't determine the time of asset generation (yet?), but enforce so called revalidation on each request. This means that even within the supposed cache lifetime of the resource, the browser checks with the remote service if the resource remains unchanged. In that case it is allowed to be used from cache, even if it's expired.

Needs to be reenabled in

• ocis-pkg/middleware/static.go and
• web/pkg/service/v0/service.go

We should check first, if the revalidation really takes place / is successful.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions.

[diocas]

Hi, maybe this ticket should be re-opened?

[pascalwengerter]

@diocas you're right. Also, if you add the bug or technical-debt label it doesn't get picked up by stalebot