SaelixCode 7b2f28f505 fix: proxy forwards browser cookie to remote causing 401; fix nodeContextMiddleware loop ...

Two backend fixes:

1. proxyReq was forwarding the browser's sencho_token cookie to the remote
   Sencho. The remote's authMiddleware uses cookieToken || bearerToken, so
   the invalid local-signed cookie was verified before the valid Bearer token,
   returning 401 on every proxied API call. Strip the cookie header in
   proxyReq so remote auth uses only the Bearer token.

2. nodeContextMiddleware blocked /api/nodes when x-node-id referenced a
   deleted node, trapping the frontend in an unrecoverable 404 loop (it
   could not fetch the nodes list to discover the node was gone). Exempt
   /api/nodes alongside /api/auth/ so the app can always self-heal.

2026-03-19 18:10:48 -04:00

..

public

feat: add frontend index.html and Vite logo; enhance system stats API with network metrics

2026-02-26 14:43:45 -05:00

src

fix: proxy forwards browser cookie to remote causing 401; fix nodeContextMiddleware loop

2026-03-19 18:10:48 -04:00

cookies.txt

feat: add alert management functionality in NotificationSettingsModal and implement stacks API endpoint

2026-02-27 09:52:54 -05:00

package-lock.json

refactor: pivot from ssh proxy to distributed api model

2026-03-19 12:20:32 -04:00

package.json

refactor: pivot from ssh proxy to distributed api model

2026-03-19 12:20:32 -04:00

tsconfig.json

Initial commit: Sencho V1 complete with Auth and Dockerization

2026-02-20 18:39:32 -05:00