From 7c668005fff737aa80ab3efa2ecdd52fc4b74137 Mon Sep 17 00:00:00 2001 From: Mattias Andrée Date: Sun, 22 Oct 2017 17:04:33 +0200 Subject: Routing keys cannot include NUL bytes MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Mattias Andrée --- README | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/README b/README index 1b92cb8..7e7be0b 100644 --- a/README +++ b/README @@ -28,12 +28,12 @@ Non-features: Routing keys: Routing keys are used to filter received messages. A routing key - may contain any byte, whoever there are three bytes with special - meaning: '*', '.', and '!'. '*' should not be used in routing keys, - but only in routing key patterns, it matches until the next '.' or - end if there are not more '.'s. Additionally if a routing key - pattern ends with '.' that '.' will match to a '.' and any - subsequent byte. For example 'a.*.c.' will match 'a.b.c.' and + may contain any byte other than the NUL, whoever there are three + bytes with special meaning: '*', '.', and '!'. '*' should not be + in routing keys, but only in routing key patterns, it matches until + the next '.' or end if there are not more '.'s. Additionally if a + routing key pattern ends with '.' that '.' will match to a '.' and + any subsequent byte. For example 'a.*.c.' will match 'a.b.c.' and 'a.b.c.d.e' but not 'a.b.c' or 'a.c.d'. And empty routing key pattern shall match everything. The token '!' is reserved, a client should never use '!' for any other purpose than specified in the -- cgit v1.2.3-70-g09d2