---
title: TCP checks: \r\n in Send data is a line break
description: The TCP Response Match card said to use \r\n for line endings, but the check sent the backslashes as typed, so a command like QUIT\r\n never ended and the…
canonical: https://watchfor.io/changelog/2026-11-18-tcp-send-data-escapes
---

[All updates](/changelog/page/2#2026-11-18-tcp-send-data-escapes) 🐛 Fixed Monitors Nov 18, 2026 · v 13.0.9

# TCP checks: \r\n in Send data is a line break

The TCP Response Match card said to use \r\n for line endings, but the check sent the backslashes as typed, so a command like QUIT\r\n never ended and the server just waited. Send data now understands the usual escapes, as Nagios check_tcp and the Prometheus blackbox exporter do: \r, \n, \t, \\ for a backslash and \xHH for one byte. What you typed is kept, and Test sends exactly what the check will.

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-11-18-tcp-send-data-escapes · Site guide: https://watchfor.io/llms.txt
