This commit contains a fixup for the original commit 64f2780a

Cache lookups will immediately register a promise to prevent multiple requests for the same ressource

Root cause: If multiple connections are opened at the same time after an update, the ui-middleware will do multiple requests to get initial data. That went especially worse, when e2e-tests are launched against ui-middlewares with multiple clients connecting at the same time.
Soltion: Make sure, that a node already caches stuff without a response.

Root cause: configuration was only reloaded on those nodes, that did the version update. The other nodes might not notice that.
Solution: On propagated version changes, the nodes always check for config changes

Root cause: cache keys handled differently when reading/writing
Solution: make sure keys are handled equally

Fixes OXUIB-1528

Use redirect instead of delivering index.html to prevent /ui paths in the future

Root cause: There are middlewares, which still use old redirects to /ui
Solution: To prevent 404s, we just serve the index.html

Solution: Only use the hash of the version

Root cause: Version has was updated before file cache
Solution: Keep all updates in one place and switch to new version at the same time

Fixes #6

Root cause: Due to the timeout, every request that was launched while fetching the previous manifests could led to another fetch and another cache.warmup
Solution: Be more synchronous

Root cause: Hash was computed on array.toString() which does not change much.
Solution: Use the actual content of the vite manifests to compute the version.

This prevents unnesessary large headers as the UI will filter for CSS files only

richard.petersen authored 3 years ago and julian.baeume committed 3 years ago

Includes the version string and dependencies

Signed-off-by: Julian Bäume <julian.baeume@open-xchange.com>

this is an implicit endpoint served by us.

remove /api prefix and be more restful. This should help to simplify ingress objects

first hit wins. This allows us to transparently use sourcemaps and other files that
are not part of the sources according to the vite manifest

this will mark the pod "ready", once the cache is warm.
This will remove the penality for the very first to this service, because
it will not receive any traffic until the cache is warm.

we want to have the changes rolled out, so we disable CSP headers for now and
will take care of them after the file_cache functionality has been rolled out

just for testing purposes, disable CSP for now until sha calculation is fixed

this currently doesn't really work as expected, but can be used as a base
to properly implement CSP for the scripts we "know" about.