2 Commits

Include renames

Author	SHA1	Message	Date
Felix KemmlerandClaude Sonnet 5	0d767d7edf	Fix infinite redirect loop on omsorgWeb behind the TLS-terminating proxy ... The root .htaccess forces HTTPS via `RewriteCond %{HTTPS} !=on`. Behind a reverse proxy that terminates TLS and forwards to Apache over plain HTTP, %{HTTPS} is always "off" - verified via mod_rewrite trace logging that this is NOT spoofable via SetEnvIf or a RewriteRule E-flag, despite that being commonly recommended; %{HTTPS} reflects only the actual TLS connection to Apache. Every request was therefore redirected to https://, which the proxy forwarded back over HTTP, looping forever (browser: "the page isn't redirecting properly"). Fix: .htaccess's redirect condition also accepts a trusted X-Forwarded-Proto: https header as evidence the request is already HTTPS. omsorgWeb/docker/000-default.conf additionally sets HTTPS=on in the request environment when that header is present, so mod_headers' `env=HTTPS` condition (HSTS header) still fires correctly - this part doesn't affect mod_rewrite's %{HTTPS} but is unrelated to the redirect fix. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-10 18:37:06 +02:00
Felix KemmlerandClaude Sonnet 5	598dfcd38a	Migrate omsorgapp to browser SPA, add Docker/CI build setup ... - omsorgapp: drop Electron, run as a plain Vite/React browser app; refresh token moves to an HttpOnly cookie (omsorgCore), CORS added for the new browser origin, document download/preview switched to Blob-based browser APIs. - Add Dockerfiles for omsorgCore, omsorgapp, and omsorgWeb, a docker-compose.yml wiring Postgres/MySQL/all three apps together, and a Gitea Actions workflow that builds and pushes images to the repo's container registry on push to main and on version tags. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-10 17:42:45 +02:00