avm/hassio-addons
1
0
Fork 0
mirror of https://github.com/alexbelgium/hassio-addons.git synced 2026-09-03 07:53:32 +02:00
Code Issues Packages Projects Releases Wiki Activity
Files
docs/skill-changelog-date-format
hassio-addons/komga/CHANGELOG.md
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

2.1 KiB
Raw Permalink Blame History

1.26.3.1 (19-08-2026)

  • Fix : tapping Read in the Home Assistant companion app opened the reader in an external browser, which carries no ingress session cookie, so Home Assistant answered 401 Unauthorized before Komga was reached (#2994). Komga opens the reader with window.open(url, '_blank') ; nginx now injects a script that turns that popup into a navigation of the ingress panel itself. Only http(s) urls below Komga's own base path are affected, so the OAuth2 login popup and links out of Komga keep their own window

1.26.3 (2026-08-13)

1.26.1.4 (12-08-2026)

  • Minor bugs fixed

1.26.1.3 (2026-08-12)

  • Fix : 401 errors after a successful login through ingress. Komga scopes its session cookies to its servlet context path (Path=/komga), which the browser never sends back from the ingress url, so every request after the login was anonymous. Nginx now rewrites the cookie path onto the ingress entry

1.26.1.2 (2026-08-12)

  • Fix : local disks (localdisks) and SMB shares failed to mount with cannot mount /dev/sdX read-only. Without an apparmor.txt the add-on ran under Docker's default AppArmor profile, which denies mount and raw block device access. Ships the same profile as the other add-ons that mount disks

1.26.1.1 (2026-08-11)

  • Bound the nginx readiness probes (--connect-timeout / --max-time) so a stalled connection cannot hang the wait, and log a warning when Komga has not answered within 15 minutes

1.26.1 (2026-08-11)

  • Initial release, based on gotson/komga (changelog)
  • Ingress support : Komga is served on the /komga servlet context path, nginx prefixes it back with the ingress entry
  • Supports local disks and SMB network shares for libraries (localdisks / networkdisks options)
  • Supports extra environment variables via the env_vars option, see the documentation