Skip to content

Commit e21f2ed

Browse files
mszabo-wikiadormando
authored andcommitted
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. NOTE (from dormando): ST was from an earlier draft of the protocol when return codes were short codes from original response types ([ST]ORED)
1 parent e2da177 commit e21f2ed

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

content/protocols/meta.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -267,7 +267,7 @@ request:
267267
ms foo S3 T360 C777 I\r\n
268268
new\r\n
269269
response:
270-
ST\r\n
270+
HD\r\n
271271
```
272272

273273
The next metaget will continue to see the item as stale, with its previous

0 commit comments

Comments
 (0)