tree 2da550bde1c2ef9fe537433d37241af1e3c222e5
parent f841ffeb361c59633afe63135ed3453e1a54ef23
author Maxim Dounin <mdounin@mdounin.ru> 1621945070 +0300
committer Maxim Dounin <mdounin@mdounin.ru> 1621945070 +0300

Resolver: explicit check for compression pointers in question.

Since nginx always uses exactly one entry in the question section of
a DNS query, and never uses compression pointers in this entry, parsing
of a DNS response in ngx_resolver_process_response() does not expect
compression pointers to appear in the question section of the DNS
response.  Indeed, compression pointers in the first name of a DNS response
hardly make sense, do not seem to be allowed by RFC 1035 (which says
"a pointer to a prior occurance of the same name", note "prior"), and
were never observed in practice.

Added an explicit check to ngx_resolver_process_response()'s parsing
of the question section to properly report an error if compression pointers
nevertheless appear in the question section.