🔌 WebSocket Bridge - Relay WebSocket Sessions Through the Server

🔌 WebSocket Connection

Enter a WebSocket URL (ws:// or wss://)

Comma-separated list of subprotocols

Tunnels the session through our server (browser → server → worker → target) instead of connecting directly. Use it for ws:// targets on this HTTPS page, servers that reject the browser Origin, or self-signed wss://. A global connection limit applies.

{{ statusIcon }} {{ statusText }}
Connected to: {{ websocketUrl }}
Mode: {{ connectionMode === 'proxy' ? '🛰️ Server proxy' : '↔️ Direct' }}

📤 Send Message

Quick Send:

📜 Message Log

No messages yet. Connect to a WebSocket server and start sending messages.
{{ message.timestamp }} {{ message.icon }}
{{ message.type }}
{{ message.content }}

📊 Connection Statistics

Messages Sent:
{{ stats.messagesSent }}
Messages Received:
{{ stats.messagesReceived }}
Connection Time:
{{ connectionTime }}
Protocol:
{{ connectedProtocol || 'N/A' }}
⚠️

ℹ️ About WebSocket Tester

WebSocket Connection Testing

WebSockets provide a persistent, full-duplex channel between a browser and server after an HTTP Upgrade handshake. The protocol is defined by RFC 6455. Use this tester to open ws:// or wss:// endpoints, send sample messages, verify subprotocol negotiation, and watch connection status in real time.

WebSocket Features

🔄 Real-time Communication

  • Bidirectional: Client and server can send messages
  • Low Latency: No HTTP request/response overhead
  • Persistent: Connection stays open until closed
  • Event-driven: Real-time message handling

🔐 Connection Security

  • WS Protocol: Unencrypted WebSocket connection
  • WSS Protocol: Encrypted WebSocket over TLS/SSL
  • Origin Policy: Cross-origin restrictions apply
  • Subprotocols: Custom application protocols

Common WebSocket Use Cases

💬 Chat Applications

Real-time messaging, typing indicators, presence status

📊 Live Data Feeds

Stock prices, sports scores, monitoring dashboards

🎮 Gaming & Collaboration

Multiplayer games, document editing, video calls

Testing Notes

  • Always use WSS (WebSocket over TLS) in production environments.
  • Browsers send an Origin header; validate it server-side before accepting sensitive cross-origin connections.
  • Test both connection establishment and message exchange, including ping/pong and close behavior.
  • Verify proper error handling, reconnect backoff, rate limits, and authentication expiry for long-running clients.
  • Reverse proxies and CDNs may need explicit WebSocket upgrade support and longer idle timeouts.
Ready