2 commits

Author	SHA1	Message	Date
Zac Gaetano	efdaa48cb6	fix: UDP upload was completely broken — relay never received sessions or chunks ... Root cause: three critical bugs in the UDP upload flow: 1. Main server never registered sessions on the relay — it stored them in its own memory but never called POST /session on the relay, so the relay had no idea about any upload sessions. 2. Relay had no HTTP chunk endpoint — the Chrome extension sends chunks via HTTP POST to /session/:id/chunk/:index, but the relay only had a binary UDP listener. Added the HTTP fallback endpoint. 3. Relay had no CORS headers — browser requests from chrome-extension:// origins were blocked. Added CORS middleware. The flow now works: Browser → POST /api/udp/session (main server) Main server → POST /session (relay, with s3Config) Browser → POST /session/:id/chunk/:n (relay, via public URL) Relay → S3 multipart upload Browser → POST /api/udp/session/:id/complete (main server) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-04-06 22:12:22 -04:00
Zac Gaetano	641701edf8	feat: Dragon Wind v1.0 — dual-mode broadcast uploader ... - Full VPM Uploader feature set (auth, users, folders, AMPP monitor) - HTTP upload via presigned S3 URLs with XHR progress tracking - UDP upload mode with relay server (WebRTC DataChannel + HTTP fallback) - S3 Admin settings with live Test Connection (upload+delete verify) - UDP Relay Admin settings with health check - Standalone UDP relay server (Node.js + Docker) with multipart S3 assembly - Chrome Extension (Manifest v3): popup, background, content script - Dynamic S3 client — reconfigures on save without restart - Dark/light theme, full AMPP job monitor - docker-compose.yml with dragon-wind + udp-relay services Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-04-05 20:05:34 -04:00