Alexandre 9302fc9a51 fix(komga): keep the reader inside the ingress panel (#2995) ...

* fix(komga): keep the reader inside the ingress panel

Komga's ui opens the reader with window.open(url, '_blank'). The Home
Assistant companion apps hand such a popup to an external browser, which
carries no ingress session cookie, so Home Assistant answers 401 before
Komga is reached.

Nginx now injects a small script into the ui shell that turns same origin
popups into a navigation in the current tab. The OAuth2 login popup, which
passes a window name and a feature string, and cross origin links are left
untouched.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* fix(komga): only intercept popups when resourceBaseUrl is known

Review feedback : the '/' fallback meant that if Komga ever stopped
setting window.resourceBaseUrl, every same origin _blank popup would be
captured -- and ingress shares the Home Assistant origin. Require the
base, and give it a trailing slash so a sibling path such as
<entry>/komgaX is not treated as being below <entry>/komga.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

2026-08-19 07:30:47 +02:00

..

cont-init.d

fix(komga): restore add-on reverted by a transient ghcr.io login failure (#2960)

2026-08-11 18:44:54 +02:00

nginx

fix(komga): keep the reader inside the ingress panel (#2995)

2026-08-19 07:30:47 +02:00

services.d

fix(komga): bound the nginx readiness probes (#2961)

2026-08-12 08:14:28 +02:00