community
/
dns
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Clarify maxCompressionPointers comment

This commit is contained in:
Tom Thorogood 2018-11-28 21:38:37 +10:30
parent 32d8e33ba2
commit d193d08243
No known key found for this signature in database
GPG Key ID: 86C63CDA416C6D2F
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
msg.go
View File

@ -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
)