mirror of
https://github.com/coredns/coredns.git
synced 2026-10-10 04:25:25 -04:00
Improve RFC links (#8612)
The `tools.ietf.org` site now redirects to `www.rfc-editor.org`. * Update various URLs to the new site. * Make links to `www.rfc-editor.org` consistent. Signed-off-by: SuperQ <superq@gmail.com>
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
|
||||
.TH "COREDNS-HTTPS" 7 "March 2026" "CoreDNS" "CoreDNS Plugins"
|
||||
.TH "COREDNS-HTTPS" 7 "October 2026" "CoreDNS" "CoreDNS Plugins"
|
||||
|
||||
.SH "NAME"
|
||||
.PP
|
||||
@@ -18,7 +18,8 @@ This plugin can only be used once per HTTPS listener block.
|
||||
|
||||
.nf
|
||||
https {
|
||||
max\_connections POSITIVE\_INTEGER
|
||||
max\_connections NON\_NEGATIVE\_INTEGER
|
||||
max\_streams NON\_NEGATIVE\_INTEGER
|
||||
}
|
||||
|
||||
.fi
|
||||
@@ -26,11 +27,13 @@ https {
|
||||
|
||||
.IP \(bu 4
|
||||
\fB\fCmax_connections\fR limits the number of concurrent TCP connections to the HTTPS server. The default value is 200 if not specified. Set to 0 for unbounded.
|
||||
.IP \(bu 4
|
||||
\fB\fCmax_streams\fR limits the number of concurrent HTTP/2 streams per HTTPS connection. This helps prevent unbounded streams on a single connection, exhausting server resources. The default value is 250 if not specified. Set to 0 to use the underlying HTTP/2 transport default.
|
||||
|
||||
|
||||
.SH "EXAMPLES"
|
||||
.PP
|
||||
Set custom limits for maximum connections:
|
||||
Set custom limits for maximum connections and streams:
|
||||
|
||||
.PP
|
||||
.RS
|
||||
@@ -40,6 +43,7 @@ https://.:443 {
|
||||
tls cert.pem key.pem
|
||||
https {
|
||||
max\_connections 100
|
||||
max\_streams 100
|
||||
}
|
||||
whoami
|
||||
}
|
||||
@@ -48,7 +52,7 @@ https://.:443 {
|
||||
.RE
|
||||
|
||||
.PP
|
||||
Set values to 0 for unbounded, matching CoreDNS behaviour before v1.14.0:
|
||||
Set both values to 0 to disable the CoreDNS limits (unbounded connections and the underlying HTTP/2 transport stream default), matching CoreDNS behaviour before v1.14.0:
|
||||
|
||||
.PP
|
||||
.RS
|
||||
@@ -58,6 +62,7 @@ https://.:443 {
|
||||
tls cert.pem key.pem
|
||||
https {
|
||||
max\_connections 0
|
||||
max\_streams 0
|
||||
}
|
||||
whoami
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user