The value is kind of arbitrary, as precaution. 64k value was causing
cqueues to close connections with GET requests with "Broken pipe"
and it seems to work with 1024 B.

This will allow modules like view etc. work in the same way with packets
received over HTTP.

We intentionally compute max-age header as minimum over all RRs, doing
so only over ANSWER section does not make sense (and RFC 8484 allows us
to do so).

This seems to be a limitation in cqueues but we have to confirm this.

First version which actually works with Firefox DoH in default
configuration.

Limitations:
- does not support HTTP GET method
- headers for HTTP cache are not generated
- error handling is largely missing
- no tests
- ACLs will not work, modules do not see source IP address of the HTTP
endpoint

Tomas Krizek authored 6 years ago and Petr Špaček committed 5 years ago

It's impossible to add managed keysets unless ta_update is loaded,
in which case ta_update.start() is called by trust_anchors.add_file().

On ta_update unload, previously managed keys are flagged as unmanaged.

It was unused since cleanup in trust_anchors and just cluttering the code.

Tomas Krizek authored 6 years ago and Petr Špaček committed 5 years ago

+ tests

Exracting RFC 5011 to separate module was a good opportunity for
cleanup.

Daniel Kahn Gillmor authored 6 years ago and Petr Špaček committed 6 years ago

For some reason, knot-resolver was shipping a copy of dygraph 2.1.0
that identified itself as 2.0.0.  This patch changes a single octet
(the minor version number) by fetching a clean copy from
http://dygraphs.com/2.1.0/dygraph.min.js.

Daniel Kahn Gillmor authored 6 years ago and Petr Špaček committed 6 years ago

Since dygraph version 2.0.0, upstream dygraph has been calling their
shipped files dygraph.min.js (see http://dygraphs.com/download.html).

Use the standard upstream name.