Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 558
    • Issues 558
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 62
    • Merge requests 62
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • KeaKea
  • Merge requests
  • !1869

Obsolete: Resolve "Connection idle timeout is not propagated down to TcpListener"

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Thomas Markwalder requested to merge 2678-connection-idle-timeout-is-not-propagated-down-to-tcplistener into master Dec 13, 2022
  • Overview 1
  • Commits 0
  • Pipelines 0
  • Changes 0

Closes #2678 (closed)

ARM needs to clarify that max-requester-idle-time is specified in milliseconds. Currently is says the default is 300 seconds but doesn't indicate that the units of the parameter are milliseconds.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: 2678-connection-idle-timeout-is-not-propagated-down-to-tcplistener