Files
Claude 7bb7175bd9 Fix 'Invalid frame header' WebSocket error with proper timeout configuration
Added Socket.IO ping/pong timeout and interval settings to maintain stable
WebSocket connections and prevent frame header errors. The error occurred when
WebSocket connections were dropped or timing out without proper keepalive.

Backend changes:
- Add ping_timeout=60 and ping_interval=25 to SocketIO config
- Enable Socket.IO logger for better debugging
- Disable verbose engineio_logger to reduce noise

Frontend changes:
- Add timeout=60000 matching backend ping_timeout
- Add reconnectionDelayMax=10000 for better reconnection handling
- Add forceNew=true to prevent connection reuse issues

All 79 tests passing with 82% coverage.

https://claude.ai/code/session_01G6aE7WxjFjUUr8nkmegitZ
2026-01-31 02:31:58 +00:00
..
2026-01-26 04:26:15 +00:00

This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.