unbound/util/data
Yorgos Thessalonikefs 73e408f1d0 A few changes for TTL processing:
- Cached messages that reach 0 TTL are considered expired. This prevents
  Unbound itself from issuing replies with TTL 0 and possibly causing a
  thundering herd at the last second. Upstream replies of TTL 0 still
  get the usual pass-through but they are not considered for caching
  from Unbound or any of its caching modules.
- 'serve-expired-reply-ttl' is changed and is now capped by the original
  TTL value of the record to try and make some sense when replying
  with expired records.
- TTL decoding was updated to adhere to RFC8767 section 4 where a set
  high-order bit means the value is positive instead of 0.
2025-09-15 10:03:35 +02:00
..
dname.c - Fix to whitespace in dname_str. 2025-08-07 16:19:10 +02:00
dname.h - Fix comment for the dname_remove_label_limit_len function. 2025-06-05 11:11:32 +02:00
msgencode.c A few changes for TTL processing: 2025-09-15 10:03:35 +02:00
msgencode.h A few changes for TTL processing: 2025-09-15 10:03:35 +02:00
msgparse.c A few changes for TTL processing: 2025-09-15 10:03:35 +02:00
msgparse.h A few changes for TTL processing: 2025-09-15 10:03:35 +02:00
msgreply.c A few changes for TTL processing: 2025-09-15 10:03:35 +02:00
msgreply.h A few changes for TTL processing: 2025-09-15 10:03:35 +02:00
packed_rrset.c A few changes for TTL processing: 2025-09-15 10:03:35 +02:00
packed_rrset.h A few changes for TTL processing: 2025-09-15 10:03:35 +02:00