From 10cc3a6a8be9f8c7cbcb045d8c462af97b3c8115 Mon Sep 17 00:00:00 2001 From: Andrew Martinez Date: Thu, 3 Jun 2021 11:39:43 -0400 Subject: [PATCH] more doc fixes for edge controller config --- etc/ctrl.with.edge.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/etc/ctrl.with.edge.yml b/etc/ctrl.with.edge.yml index 77859c20d..683d68c08 100644 --- a/etc/ctrl.with.edge.yml +++ b/etc/ctrl.with.edge.yml @@ -153,17 +153,17 @@ web: # Allows the specification of webListener level options - mainly dealing with HTTP/TLS settings. These options are # used for all http servers started by the current webListener. options: - # idleTimeoutMs - optional, default 5000ms + # idleTimeout - optional, default 5000ms # The maximum amount of idle time in milliseconds allowed for pipelined HTTP requests. Setting this too high # can cause resources on the host to be consumed as clients remain connected and idle. Lowering this value # will cause clients to reconnect on subsequent HTTPs requests. idleTimeout: 5000ms #http timeouts, new - # readTimeoutMs - optional, default 5000ms + # readTimeout - optional, default 5000ms # The maximum amount of time in milliseconds http servers will wait to read the first incoming requests. A higher # value risks consuming resources on the host with clients that are acting bad faith or suffering from high latency # or packet loss. A lower value can risk losing connections to high latency/packet loss clients. readTimeout: 5000ms - # writeTimeoutMs - optional, default 10000ms + # writeTimeout - optional, default 10000ms # The total maximum time in milliseconds that the http server will wait for a single requests to be received and # responded too. A higher value can allow long running requests to consume resources on the host. A lower value # can risk ending requests before the server has a chance to respond.