- Sep 12, 2022
-
-
richard.petersen authored
Root cause: Express automatically redirected, fastify does not Solution: Manually do the redirect
-
- Sep 09, 2022
-
-
- Sep 06, 2022
-
-
richard.petersen authored
-
richard.petersen authored
-
- Sep 02, 2022
-
-
richard.petersen authored
-
richard.petersen authored
This commit contains a fixup for the original commit 64f2780a
-
- Sep 01, 2022
-
-
richard.petersen authored
-
- Aug 17, 2022
-
-
richard.petersen authored
-
- Jul 18, 2022
-
-
richard.petersen authored
-
- May 24, 2022
-
-
richard.petersen authored
Cache lookups will immediately register a promise to prevent multiple requests for the same ressource
-
- May 16, 2022
-
-
richard.petersen authored
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.
-
- May 09, 2022
-
-
richard.petersen authored
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
-
- May 05, 2022
-
-
richard.petersen authored
-
- May 04, 2022
-
-
richard.petersen authored
-
richard.petersen authored
-
- Apr 04, 2022
-
-
julian.baeume authored
Root cause: cache keys handled differently when reading/writing Solution: make sure keys are handled equally Fixes OXUIB-1528
-
- Mar 14, 2022
-
-
richard.petersen authored
-
richard.petersen authored
-
- Mar 01, 2022
-
-
richard.petersen authored
Use redirect instead of delivering index.html to prevent /ui paths in the future
-
- Feb 28, 2022
-
-
richard.petersen authored
Root cause: There are middlewares, which still use old redirects to /ui Solution: To prevent 404s, we just serve the index.html
-
richard.petersen authored
-
richard.petersen authored
Solution: Only use the hash of the version
-
richard.petersen authored
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
-
- Feb 23, 2022
-
-
richard.petersen authored
-
richard.petersen authored
-
richard.petersen authored
-
richard.petersen authored
-
- Feb 08, 2022
-
-
richard.petersen authored
-
richard.petersen authored
Fixes #6
-
- Jan 26, 2022
-
-
richard.petersen authored
-
- Jan 12, 2022
-
-
richard.petersen authored
-
- Jan 11, 2022
-
-
richard.petersen authored
-
- Nov 29, 2021
-
-
-
richard.petersen authored
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
-
- Nov 25, 2021
-
-
richard.petersen authored
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.
-
- Nov 11, 2021
-
-
richard.petersen authored
This prevents unnesessary large headers as the UI will filter for CSS files only
-
- Nov 09, 2021
-
-
Includes the version string and dependencies Signed-off-by:
Julian Bäume <julian.baeume@open-xchange.com>
-
- Oct 13, 2021
-
-
julian.baeume authored
this is an implicit endpoint served by us.
-
- Oct 08, 2021
-
-
julian.baeume authored
remove /api prefix and be more restful. This should help to simplify ingress objects
-
julian.baeume authored
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
-