JamesFlare1212 71116f9f6e fix(auth): treat 5xx as cookie expiration and re-login immediately
KEY DISCOVERY: 5xx errors are early signs of cookie expiration.
The backend returns 500 when cookie is expired but session not yet invalidated.
It takes several hours before it returns 401/403.

CHANGES:
1. On 5xx: throw AuthenticationError to trigger immediate re-login
2. Removed cookie validation logic (no longer needed)
3. Cache still preserved during re-login process
4. Re-login happens within same request, not on next request

This fixes the issue where expired cookies would cause 5xx errors
for hours before any re-login attempt was made.
2026-04-11 10:55:31 -04:00
2025-05-12 21:45:57 -04:00
2026-04-07 18:19:13 -04:00
2026-04-07 18:19:13 -04:00
2025-05-10 23:39:39 -04:00
2025-05-10 23:39:39 -04:00

How to Run

copy example.env

cp example.env .env

edit .env

API_USERNAME is your engage username in URL-encode.
API_PASSWORD is your engage password in URL-encode.

Description
No description provided
Readme 639 KiB
Languages
TypeScript 98.1%
Dockerfile 1.1%
Shell 0.8%