Vantz Stockwell c4d7ad1833 fix: WebSocket auth always fails — client object has no URL property ... With the NestJS ws adapter, the JWT token URL is on the HTTP upgrade request (second arg to handleConnection), not on the WebSocket client object. client.url was undefined, new URL(undefined) threw, catch returned null, and every connection got 4001 Unauthorized. Fix: Pass the IncomingMessage req to validateClient and prefer req.url. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>		2026-03-13 11:16:03 -04:00
..
prisma	feat: nav bar (Home link), profile management, TOTP 2FA	2026-03-13 08:36:03 -04:00
src	fix: WebSocket auth always fails — client object has no URL property	2026-03-13 11:16:03 -04:00
test	feat: AES-256-GCM encryption service + auth module (JWT, guards, seed)	2026-03-12 17:07:14 -04:00
nest-cli.json	feat: project scaffold — Docker, NestJS, Nuxt 3, Prisma config	2026-03-12 17:05:37 -04:00
package-lock.json	feat: nav bar (Home link), profile management, TOTP 2FA	2026-03-13 08:36:03 -04:00
package.json	feat: nav bar (Home link), profile management, TOTP 2FA	2026-03-13 08:36:03 -04:00
seed.js	fix: auto-run Prisma migrate + seed on container startup	2026-03-13 08:19:46 -04:00
tsconfig.build.json	feat: project scaffold — Docker, NestJS, Nuxt 3, Prisma config	2026-03-12 17:05:37 -04:00
tsconfig.json	feat: project scaffold — Docker, NestJS, Nuxt 3, Prisma config	2026-03-12 17:05:37 -04:00