Integration · Group 9 of 9

Raw bytes and TLS connection timing

Five named cases from the tracked correctness inventory, kept on one focused page.

5 exact casesInventory source: test suite

Exact current cases

  1. preserves invalid UTF-8 from client to server
  2. preserves invalid UTF-8 from server to client
  3. treats delimiter and NUL bytes as raw payload data
  4. requires explicit TLS server credentials
  5. publishes connect only after the TLS handshake

Inventory and execution

What this page proves

These are the exact names registered by the source inventory for this group.

What proves a pass

The generated workflow result on the testing overview is authoritative about execution and failures.