annotate src/core/ngx_murmurhash.h @ 8484:3e78c12d4f37
stable-1.20
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.
author |
Maxim Dounin <mdounin@mdounin.ru> |
date |
Tue, 25 May 2021 15:17:50 +0300 |
parents |
709d7d24239d |
children |
|
rev |
line source |
3891
|
1
|
|
2 /*
|
|
3 * Copyright (C) Igor Sysoev
|
4412
|
4 * Copyright (C) Nginx, Inc.
|
3891
|
5 */
|
|
6
|
|
7
|
|
8 #ifndef _NGX_MURMURHASH_H_INCLUDED_
|
|
9 #define _NGX_MURMURHASH_H_INCLUDED_
|
|
10
|
|
11
|
|
12 #include <ngx_config.h>
|
|
13 #include <ngx_core.h>
|
|
14
|
|
15
|
|
16 uint32_t ngx_murmur_hash2(u_char *data, size_t len);
|
|
17
|
|
18
|
4575
|
19 #endif /* _NGX_MURMURHASH_H_INCLUDED_ */
|