Root cause: Express automatically redirected, fastify does not
Solution: Manually do the redirect

Root cause: mime types might contain charset information
Solution: be more relaxed about anything following the actual mime type

This commit contains a fixup for the original commit 64f2780a

richard.petersen authored 2 years ago and richard.petersen committed 2 years ago

Only warn, when meta.json is missing since the ui-middleware will fall back to a computed hash value

alexander.quast authored 2 years ago and richard.petersen committed 2 years ago

Changelog:
 - Changed all 'trace' logs to level 'debug'
 - Added logging to the version check functions on log level 'info' and 'debug'
 - Added some time measures on ready checks to see what's taking so long on startup

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

Use correct path for index.html for the memory lookup

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