netty5/codec-dns/src/test/java/io/netty/handler/codec/dns
Norman Maurer 1a53df1031 Detect truncated responses caused by EDNS0 and MTU miss-match (#9468)
Motivation:

It is possible that the user uses a too big EDNS0 setting for the MTU and so we may receive a truncated datagram packet. In this case we should try to detect this and retry via TCP if possible

Modifications:

- Fix detecting of incomplete records
- Mark response as truncated if we did not consume the whole packet
- Add unit test

Result:

Fixes https://github.com/netty/netty/issues/9365
2019-08-17 09:58:40 +02:00
..
AbstractDnsRecordTest.java [#4993] Correctly handle trailing dot in DNS requests and responses for the hostname. 2016-03-22 12:30:46 +01:00
DefaultDnsRecordDecoderTest.java Detect truncated responses caused by EDNS0 and MTU miss-match (#9468) 2019-08-17 09:58:40 +02:00
DefaultDnsRecordEncoderTest.java Java 8 migration. Remove ThreadLocalProvider and inline java.util.concurrent.ThreadLocalRandom.current() where necessary. (#8762) 2019-01-22 20:14:28 +01:00
DnsQueryTest.java Java 8 migration: Use diamond operator (#8749) 2019-01-22 16:07:26 +01:00
DnsRecordTypeTest.java Java 8 migration: Use diamond operator (#8749) 2019-01-22 16:07:26 +01:00
DnsResponseTest.java fix the typos 2017-04-20 04:56:09 +02:00