Skip to content

fix(http): replace cached HTTPS DNS records - #971

Merged
ryanfowler merged 1 commit into
mainfrom
fix/http3-cache-https-replacement
Aug 8, 2026
Merged

fix(http): replace cached HTTPS DNS records#971
ryanfowler merged 1 commit into
mainfrom
fix/http3-cache-https-replacement

Conversation

@ryanfowler

Copy link
Copy Markdown
Owner

Summary

  • replace cached DNS-derived HTTP/3 candidates after successful HTTPS RRset lookups
  • clear stale DNS candidates on NODATA while preserving them on lookup failure
  • keep Alt-Svc candidates independent and improve system lookup error classification

Validation

  • cargo fmt --check
  • cargo clippy --locked --all-targets --all-features -- -D warnings
  • cargo test --locked --all-features --lib --bins
  • full integration test suite with --test-threads=2

@ryanfowler
ryanfowler enabled auto-merge (squash) August 8, 2026 10:56
Replace the previous HTTPS RRset after a successful lookup, including NODATA responses. Preserve cached DNS candidates when discovery fails, while continuing to race fresh discovery against Alt-Svc candidates.
@ryanfowler
ryanfowler force-pushed the fix/http3-cache-https-replacement branch from 900c2b5 to 01181f6 Compare August 8, 2026 11:00
@ryanfowler
ryanfowler merged commit 506f89a into main Aug 8, 2026
7 of 8 checks passed
@ryanfowler
ryanfowler deleted the fix/http3-cache-https-replacement branch August 8, 2026 11:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant