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

Change the prefix to reflect the "new" name of the service. May be this even should be configurable at some point.

This is a breaking change.

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

Fixes OXUIB-1528

Root cause: Cross-Origin-Opener-Policy is set to same-origin per default and will prevent parent or window.opener to be set
Solution: Set Cross-Origin-Opener-Policy to same-origin-allow popups

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

Root cause: If some of the UI containers is not available after successful start, the version update check might fail.
Solution: Add error handlers when manifests can not be fetched after startup

Fixes #6

Root cause: Every readiness check triggered a cache warming
Solution: Move readiness to startup probe

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 can not only be handled on ingress level, but we need to mount the
express app also on the app root level. This basically just works out of the
box.

Promise.race resolve or rejects with the first promise that answers.
We now return the first promise that fulfills after all promises have
settled.