Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

dnsdist: setMaxTCPConnectionsPerClient is not applied to DoH connections #12019

Closed
rgacogne opened this issue Sep 26, 2022 · 0 comments · Fixed by #12483
Closed

dnsdist: setMaxTCPConnectionsPerClient is not applied to DoH connections #12019

rgacogne opened this issue Sep 26, 2022 · 0 comments · Fixed by #12483
Assignees
@rgacogne
Labels
defect dnsdist
Milestone
dnsdist-1.8.0

Comments

@rgacogne
Copy link
Member

  • Program: dnsdist
  • Issue type: Bug report

Short description

The setMaxTCPConnectionsPerClient directive can be used to "set the maximum number of TCP connections per client", which I would expect to include TCP, DoT but also DoH connections, and as of today it only includes TCP and DoT.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rgacogne rgacogne

Labels
defect dnsdist
Projects
None yet
Milestone
dnsdist-1.8.0
Development

Successfully merging a pull request may close this issue.

dnsdist: Apply the max number of concurrent conns per client to DoH rgacogne/pdns
1 participant
@rgacogne