From d193d08243898abb22d376e46ce7145a37f6bf06 Mon Sep 17 00:00:00 2001 From: Tom Thorogood Date: Wed, 28 Nov 2018 21:38:37 +1030 Subject: [PATCH] Clarify maxCompressionPointers comment --- msg.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/msg.go b/msg.go index e7572c71..f96a7d19 100644 --- a/msg.go +++ b/msg.go @@ -33,8 +33,8 @@ const ( // // It is possible to construct a valid message that has more compression pointers // than this, and still doesn't loop, by pointing to a previous pointer. This is - // not something a well written implementation should ever do, so we ignore that - // possibility. + // not something a well written implementation should ever do, so we leave them + // to trip the maximum compression pointer check. maxCompressionPointers = (maxDomainNameWireOctets+1)/2 - 2 )