mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-10 20:56:39 +00:00
kevinveenbirkenbachandClaude Opus 5.5
a4932f6a40
CI run 40979252521 Taiga#0 picked the onion sibling and failed five specs (test-login-oidc, test-themed-routes, network-leak, design:242/263). - Login: TAIGA_COOKIE_SECURE renders True once clearnet has TLS, so taiga-back marks sessionid and csrftoken Secure. Chromium drops them on the plaintext onion, the /oidc/callback/ arrives without a session and mozilla-django-oidc falls into login_failure() (gateway log: the 302 to /login?type=oidc&error=None six times, no sessionid on the callback in the trace). The plaintext sibling vhost now strips Secure from both cookies via proxy_cookie_flags, wired as webserver_location_extra_ configuration like Semaphore; TAIGA_COOKIE_SECURE is pinned to the canonical domain so the per-vhost tls lookup cannot flip it. - Logo: the design sheet embedded absolute clearnet CDN URLs, rendered once and served to both siblings. It now uses design.relative_urls, served same-origin under /_infinito/cdn/; the spec resolves the logo URLs against page.url(). A local compose deploy that picked the onion passed all five specs (19 passed); the onion vhost carries both proxy_cookie_flags lines, the clearnet vhost none. test_onion_sibling.py renders the real vars through Ansible's Templar; reverting TAIGA_COOKIE_SECURE fails two of its cases. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>