HTTP, WS, and TCP
Select the endpoint type that matches the source protocol. Pubto does not convert an HTTP service into TCP or make a browser API compatible simply because its address is reachable.
Before you begin
Identify the exact source scheme, host, port, and expected client. For browser APIs, also identify the frontend origin, request method, and custom headers before diagnosing CORS or CSRF behavior.
Shortest path
pubto publish --port 8080
pubto publish --ws-port 8998
pubto publish --tcp 3306HTTP and HTTPS
Use these for demos, web products, REST or GraphQL APIs, webhooks, and other request-response services. Verify a safe public route without application credentials before sharing it.
WebSocket
Use WS or WSS for bidirectional browser and application streams. Check the 101 upgrade separately and ensure the source accepts the intended public Origin.
TCP
Use TCP for MySQL, PostgreSQL, Redis, SSH, MQTT, and other byte streams. A TCP publication is a raw socket address, not a browser URL, and requires the source service's own authentication and encryption.
Before you share
- Endpoint type matches the source protocol
- The source allows the intended public origin or client
- TCP targets use their own credentials and TLS
- The endpoint was verified with the correct client
A successful HTTP response proves reachability, not full browser compatibility. CORS, CSRF, cookies, WebSocket Origin policy, and application authentication remain responsibilities of the source.