Skip to main content

TCP (Developer View)

A long-lived connection oriented around byte streams. Once connected you have a persistent two-way channel; what you get back depends on the server's framing rules.

How to Use in the UI​

  1. Create a TCP request: host 127.0.0.1, port 18086 (TCP URLs store the host; the port is stored separately).
  2. Tap Connect to establish the session.
  3. Send text, or send binary (passed as base64, for length-prefixed and similar framing protocols).
  4. Received data displays in real time; close when done.

Plain vs Encrypted​

  • tcp:// is plaintext; tcps:// uses TLS (configure TLS via an encrypted Pre-URL or imported certificates).

Framing (Coalescing / Splitting)​

TCP is a stream with no natural message boundaries. The tool supports framing by delimiter / fixed length / length field (LV), and the sample server ports include matching scenarios (the automated case tcp.framing-line covers line-based framing, etc.).

Verified Behavior​

hello-tcp-世界 round-trips identically (UTF-8 intact). Text and bytesBase64 are mutually exclusive: sending binary goes through base64.

Gotchas​

  • Connect without sending: after connecting you can directly watch server pushes.
  • Long connections occupy session quota and are reclaimed when idle; remember to close them after debugging.

Related: UDP in udp.