From 1ae990b55f1da111b29964165bcc883bdc41dad2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?M=C3=A1t=C3=A9=20Szab=C3=B3?= Date: Thu, 26 Feb 2026 01:56:04 +0100 Subject: [PATCH] Fix example response for stale metaset From some quick testing this seems to yield `HD` not `ST`: ``` $ printf 'mg foo t c f v\r\n' | nc -N 127.0.0.1 11213 VA 3 t3572 c21 f0 w4t $ printf 'ms foo 3 T3600 C20 I\r\nw5t\r\n' | nc -N 127.0.0.1 11213 HD $ printf 'mg foo t c f v\r\n' | nc -N 127.0.0.1 11213 VA 3 t3549 c22 f0 X W w5t ``` protocol.txt also doesn't mention an `ST` response for metasets. --- content/protocols/meta.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/protocols/meta.md b/content/protocols/meta.md index 69cb83f..a63da4f 100644 --- a/content/protocols/meta.md +++ b/content/protocols/meta.md @@ -267,7 +267,7 @@ request: ms foo S3 T360 C777 I\r\n new\r\n response: - ST\r\n + HD\r\n ``` The next metaget will continue to see the item as stale, with its previous