From 86fb4978c6e1c3d66d2061b886e525422072b398 Mon Sep 17 00:00:00 2001 From: kong-kiransharma Date: Fri, 10 Apr 2026 13:38:30 +0530 Subject: [PATCH 01/10] Create About-retries-attribute-of-service-object.md first article to test and document the end to end process --- ...out-retries-attribute-of-service-object.md | 170 ++++++++++++++++++ 1 file changed, 170 insertions(+) create mode 100644 docs/support/About-retries-attribute-of-service-object.md diff --git a/docs/support/About-retries-attribute-of-service-object.md b/docs/support/About-retries-attribute-of-service-object.md new file mode 100644 index 0000000000..e9c634f33e --- /dev/null +++ b/docs/support/About-retries-attribute-of-service-object.md @@ -0,0 +1,170 @@ +--- +# REQUIRED: The title that appears at the top of the page +title: About retries attribute of service object + +# REQUIRED: Must be set to "support" for support articles +content_type: support + +# OPTIONAL: A brief description of what this support article covers +# This appears in search results and meta tags +description: About retries attribute of service object. + +# OPTIONAL: Which Kong products this article applies to +# Common values: gateway, konnect, mesh, insomnia, deck +products: + - gateway + +# REQUIRED for Gateway support articles (when products includes "gateway"); OPTIONAL otherwise +# accepted values: on-prem, konnect +works_on: + - on-prem + - konnect + + +# OPTIONAL: Related resources that provide additional context +# Each entry should have a text label and a url +related_resources: + - text: Link text for related documentation + url: /path/to/related/page/ + - text: Another related resource + url: /path/to/another/page/ + +# OPTIONAL: TL;DR section that appears at the top of the article +# Provides a quick question and answer summary +tldr: + q: retries attribute of service object + a: | + The articles describe the end-to-end steps of working with service object + +--- + +Below is an example of installing Kong on Docker. + +Please install Kong on Docker by following the official guide: Kong Docker Installation . + +## 1. How to check the behavior of the + +``` +retries +``` + +attribute? + +Step 1: Set + +``` +KONG_LOG_LEVEL=debug +``` + +and reload Kong. + +In your container, set + +``` +KONG_LOG_LEVEL +``` + +to + +``` +debug +``` + +: + +```bash +$ echo "KONG_LOG_LEVEL=debug kong reload exit" | docker exec -i kong-ee /bin/sh +``` + +Step 2: Run the httpbin container. + +```bash +$ docker run -d --name httpbin --network=kong-ee-net -p 80:80 kennethreitz/httpbin +``` + +Step 3: Create a service object linked to the httpbin container, setting + +``` +retries +``` + +(e.g., 5): + +```bash +$ curl -i -X POST http://localhost:8001/services \ + --data name=example_service \ + --data url='http://httpbin/anything' \ + --data retries=5 +``` + +Step 4: Create a route object for the above service: + +```bash +$ curl -i -X POST http://localhost:8001/services/example_service/routes \ + --data 'paths[]=/mock' \ + --data name=mocking +``` + +Step 5: Access the route successfully, receiving a 200 response: + +```bash +$ curl localhost:8000/mock -i + +HTTP/1.1 200 OK +Content-Type: application/json +Content-Length: 406 +Connection: keep-alive +Server: gunicorn/19.9.0 +Date: Thu, 08 Apr 2021 06:44:09 GMT +Access-Control-Allow-Origin: * +Access-Control-Allow-Credentials: true +X-Kong-Upstream-Latency: 13 +X-Kong-Proxy-Latency: 4 +Via: kong/2.3.3.0-enterprise-edition +... +``` + +Step 6: Stop the httpbin container, then access the route again: + +```bash +$ docker stop httpbin +$ curl localhost:8000/mock -i + +HTTP/1.1 502 Bad Gateway +Server: openresty +Date: Thu, 08 Apr 2021 06:48:30 GMT +Content-Type: application/json; charset=utf-8 +Connection: keep-alive +Content-Length: 75 +X-Kong-Upstream-Latency: 3071 +X-Kong-Proxy-Latency: 30607 +Via: kong/2.3.3.0-enterprise-edition + +{ + "message":"An invalid response was received from the upstream server" +} +``` + +You can check the Kong logs to observe retry attempts, as shown below: + +```bash +$ docker logs -f kong-ent + +DATE [debug] ... balancer(): setting address (try 1): xxx.xxx.xxx.xxx:xxx +... +... +DATE [error] ... connect() failed (110: Operation timed out) while connecting to upstream, client: xxx.xxx.xxx.xxx, server: kong, request: "GET /xxx HTTP/1.1", upstream: "xxx", host: "xxx" +DATE [debug] ... balancer(): setting address (try 2): xxx.xxx.xxx.xxx:xxx +... +... +``` + +## 2. Does the service object only retry when an upstream object is set? + +No, the service object can retry requests even if an upstream object has not been set. + +## 3. Does the service object retry on HTTP 4xx/5xx responses? + +No, retries happen only for TCP connection errors. However, Kong can perform HTTP and TCP health checks using the upstream object. For more details, see the Health Checks and Circuit Breakers documentation . + + From afdff9f2e815fd55ca464dfc2d7e9898c4ce4c9f Mon Sep 17 00:00:00 2001 From: kong-kiransharma Date: Mon, 13 Apr 2026 17:54:31 +0530 Subject: [PATCH 02/10] Update About-retries-attribute-of-service-object.md --- ...out-retries-attribute-of-service-object.md | 46 ++++--------------- 1 file changed, 8 insertions(+), 38 deletions(-) diff --git a/docs/support/About-retries-attribute-of-service-object.md b/docs/support/About-retries-attribute-of-service-object.md index e9c634f33e..1c2a1ba291 100644 --- a/docs/support/About-retries-attribute-of-service-object.md +++ b/docs/support/About-retries-attribute-of-service-object.md @@ -42,53 +42,23 @@ Below is an example of installing Kong on Docker. Please install Kong on Docker by following the official guide: Kong Docker Installation . -## 1. How to check the behavior of the +## 1. How to check the behavior of the retries attribute? -``` -retries -``` - -attribute? - -Step 1: Set - -``` -KONG_LOG_LEVEL=debug -``` - -and reload Kong. - -In your container, set - -``` -KONG_LOG_LEVEL -``` - -to - -``` -debug -``` +**Step 1**: Set KONG_LOG_LEVEL=debug and reload Kong. -: +In your container, set KONG_LOG_LEVEL to **debug** ```bash $ echo "KONG_LOG_LEVEL=debug kong reload exit" | docker exec -i kong-ee /bin/sh ``` -Step 2: Run the httpbin container. +**Step 2**: Run the httpbin container. ```bash $ docker run -d --name httpbin --network=kong-ee-net -p 80:80 kennethreitz/httpbin ``` -Step 3: Create a service object linked to the httpbin container, setting - -``` -retries -``` - -(e.g., 5): +**Step 3**: Create a service object linked to the httpbin container, setting retries ```bash $ curl -i -X POST http://localhost:8001/services \ @@ -97,7 +67,7 @@ $ curl -i -X POST http://localhost:8001/services \ --data retries=5 ``` -Step 4: Create a route object for the above service: +**Step 4**: Create a route object for the above service: ```bash $ curl -i -X POST http://localhost:8001/services/example_service/routes \ @@ -105,7 +75,7 @@ $ curl -i -X POST http://localhost:8001/services/example_service/routes \ --data name=mocking ``` -Step 5: Access the route successfully, receiving a 200 response: +**Step 5**: Access the route successfully, receiving a 200 response: ```bash $ curl localhost:8000/mock -i @@ -124,7 +94,7 @@ Via: kong/2.3.3.0-enterprise-edition ... ``` -Step 6: Stop the httpbin container, then access the route again: +**Step 6**: Stop the httpbin container, then access the route again: ```bash $ docker stop httpbin From 23736c875eba86902a48f762ad764ba0e13591d4 Mon Sep 17 00:00:00 2001 From: kong-kiransharma Date: Tue, 14 Apr 2026 01:16:38 +0530 Subject: [PATCH 03/10] Update About-retries-attribute-of-service-object.md --- ...out-retries-attribute-of-service-object.md | 30 +++++-------------- 1 file changed, 8 insertions(+), 22 deletions(-) diff --git a/docs/support/About-retries-attribute-of-service-object.md b/docs/support/About-retries-attribute-of-service-object.md index 1c2a1ba291..72e7a1d7a3 100644 --- a/docs/support/About-retries-attribute-of-service-object.md +++ b/docs/support/About-retries-attribute-of-service-object.md @@ -1,13 +1,10 @@ --- # REQUIRED: The title that appears at the top of the page -title: About retries attribute of service object +title: How do I check the behavior of the retries attribute? # REQUIRED: Must be set to "support" for support articles content_type: support -# OPTIONAL: A brief description of what this support article covers -# This appears in search results and meta tags -description: About retries attribute of service object. # OPTIONAL: Which Kong products this article applies to # Common values: gateway, konnect, mesh, insomnia, deck @@ -21,25 +18,16 @@ works_on: - konnect -# OPTIONAL: Related resources that provide additional context -# Each entry should have a text label and a url -related_resources: - - text: Link text for related documentation - url: /path/to/related/page/ - - text: Another related resource - url: /path/to/another/page/ # OPTIONAL: TL;DR section that appears at the top of the article # Provides a quick question and answer summary tldr: - q: retries attribute of service object + q: How do I check the behavior of the retries attribute? a: | - The articles describe the end-to-end steps of working with service object + When an upstream is unreachable, Kong retries the connection up to the configured number of times. You can observe this in debug logs. --- -Below is an example of installing Kong on Docker. - Please install Kong on Docker by following the official guide: Kong Docker Installation . ## 1. How to check the behavior of the retries attribute? @@ -128,13 +116,11 @@ DATE [debug] ... balancer(): setting address (try 2): xxx.xxx.xxx.xxx:xxx ... ... ``` +faqs: +-q: Does the service object only retry when an upstream object is set? + a: No, the service object can retry requests even if an upstream object has not been set. -## 2. Does the service object only retry when an upstream object is set? - -No, the service object can retry requests even if an upstream object has not been set. - -## 3. Does the service object retry on HTTP 4xx/5xx responses? - -No, retries happen only for TCP connection errors. However, Kong can perform HTTP and TCP health checks using the upstream object. For more details, see the Health Checks and Circuit Breakers documentation . +-q: Does the service object retry on HTTP 4xx/5xx responses? + a:No, retries happen only for TCP connection errors. However, Kong can perform HTTP and TCP health checks using the upstream object. For more details, see the Health Checks and Circuit Breakers documentation . From 8f315265a3541bb38c092540ac451b30e1bf31c7 Mon Sep 17 00:00:00 2001 From: kong-kiransharma Date: Tue, 14 Apr 2026 01:19:10 +0530 Subject: [PATCH 04/10] Update About-retries-attribute-of-service-object.md --- docs/support/About-retries-attribute-of-service-object.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/support/About-retries-attribute-of-service-object.md b/docs/support/About-retries-attribute-of-service-object.md index 72e7a1d7a3..8a7eddf33c 100644 --- a/docs/support/About-retries-attribute-of-service-object.md +++ b/docs/support/About-retries-attribute-of-service-object.md @@ -1,6 +1,6 @@ --- # REQUIRED: The title that appears at the top of the page -title: How do I check the behavior of the retries attribute? +title: How to check the behavior of the retries attribute? # REQUIRED: Must be set to "support" for support articles content_type: support From d6840cfda367278da670547fa069d58f772c4f3b Mon Sep 17 00:00:00 2001 From: kong-kiransharma Date: Tue, 14 Apr 2026 01:25:01 +0530 Subject: [PATCH 05/10] Update About-retries-attribute-of-service-object.md --- docs/support/About-retries-attribute-of-service-object.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/support/About-retries-attribute-of-service-object.md b/docs/support/About-retries-attribute-of-service-object.md index 8a7eddf33c..b4bf4e5205 100644 --- a/docs/support/About-retries-attribute-of-service-object.md +++ b/docs/support/About-retries-attribute-of-service-object.md @@ -117,10 +117,10 @@ DATE [debug] ... balancer(): setting address (try 2): xxx.xxx.xxx.xxx:xxx ... ``` faqs: --q: Does the service object only retry when an upstream object is set? - a: No, the service object can retry requests even if an upstream object has not been set. + -q: Does the service object only retry when an upstream object is set? + a: No, the service object can retry requests even if an upstream object has not been set. --q: Does the service object retry on HTTP 4xx/5xx responses? - a:No, retries happen only for TCP connection errors. However, Kong can perform HTTP and TCP health checks using the upstream object. For more details, see the Health Checks and Circuit Breakers documentation . + -q: Does the service object retry on HTTP 4xx/5xx responses? + a:No, retries happen only for TCP connection errors. However, Kong can perform HTTP and TCP health checks using the upstream object. For more details, see the Health Checks and Circuit Breakers documentation . From 5dda810b22c52d377299e1f2c905af9e5c90026a Mon Sep 17 00:00:00 2001 From: kong-kiransharma Date: Tue, 14 Apr 2026 01:28:31 +0530 Subject: [PATCH 06/10] Update About-retries-attribute-of-service-object.md --- .../About-retries-attribute-of-service-object.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/support/About-retries-attribute-of-service-object.md b/docs/support/About-retries-attribute-of-service-object.md index b4bf4e5205..2bba3c8914 100644 --- a/docs/support/About-retries-attribute-of-service-object.md +++ b/docs/support/About-retries-attribute-of-service-object.md @@ -116,11 +116,11 @@ DATE [debug] ... balancer(): setting address (try 2): xxx.xxx.xxx.xxx:xxx ... ... ``` -faqs: - -q: Does the service object only retry when an upstream object is set? - a: No, the service object can retry requests even if an upstream object has not been set. - - -q: Does the service object retry on HTTP 4xx/5xx responses? - a:No, retries happen only for TCP connection errors. However, Kong can perform HTTP and TCP health checks using the upstream object. For more details, see the Health Checks and Circuit Breakers documentation . - +faqs: + - q: Does the service object only retry when an upstream object is set? + a: No, the service object can retry requests even if an upstream object has not been set. + + - q: Does the service object retry on HTTP 4xx/5xx responses? + a: No, retries happen only for TCP connection errors. However, Kong can perform HTTP and TCP health checks using the upstream object. For more details, see the Health Checks and Circuit Breakers documentation. + From 155080ba3aebe1108fcf845f4887dbd580a78bc3 Mon Sep 17 00:00:00 2001 From: kong-kiransharma Date: Tue, 14 Apr 2026 01:31:46 +0530 Subject: [PATCH 07/10] Update About-retries-attribute-of-service-object.md --- docs/support/About-retries-attribute-of-service-object.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/support/About-retries-attribute-of-service-object.md b/docs/support/About-retries-attribute-of-service-object.md index 2bba3c8914..0a6717add4 100644 --- a/docs/support/About-retries-attribute-of-service-object.md +++ b/docs/support/About-retries-attribute-of-service-object.md @@ -1,6 +1,6 @@ --- # REQUIRED: The title that appears at the top of the page -title: How to check the behavior of the retries attribute? +title: How to check the behavior of retries attribute? # REQUIRED: Must be set to "support" for support articles content_type: support From 620854dac4f35d2f0f7bb0456a6782fbb6466bdf Mon Sep 17 00:00:00 2001 From: kong-kiransharma Date: Tue, 14 Apr 2026 01:34:13 +0530 Subject: [PATCH 08/10] Update About-retries-attribute-of-service-object.md --- docs/support/About-retries-attribute-of-service-object.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/support/About-retries-attribute-of-service-object.md b/docs/support/About-retries-attribute-of-service-object.md index 0a6717add4..846e53a1ff 100644 --- a/docs/support/About-retries-attribute-of-service-object.md +++ b/docs/support/About-retries-attribute-of-service-object.md @@ -28,9 +28,7 @@ tldr: --- -Please install Kong on Docker by following the official guide: Kong Docker Installation . - -## 1. How to check the behavior of the retries attribute? +Please install Kong on Docker by following the official guide: Kong Docker Installation. **Step 1**: Set KONG_LOG_LEVEL=debug and reload Kong. From 460cfe899b734036017b2004f83c39139a88725b Mon Sep 17 00:00:00 2001 From: Angel Date: Mon, 13 Apr 2026 16:59:06 -0400 Subject: [PATCH 09/10] fix the file so it renders, and add comments. --- ...out-retries-attribute-of-service-object.md | 106 +++++++++++++++ app/support.html | 49 +++++++ ...out-retries-attribute-of-service-object.md | 124 ------------------ 3 files changed, 155 insertions(+), 124 deletions(-) create mode 100644 app/_support/About-retries-attribute-of-service-object.md create mode 100644 app/support.html delete mode 100644 docs/support/About-retries-attribute-of-service-object.md diff --git a/app/_support/About-retries-attribute-of-service-object.md b/app/_support/About-retries-attribute-of-service-object.md new file mode 100644 index 0000000000..105cd3f466 --- /dev/null +++ b/app/_support/About-retries-attribute-of-service-object.md @@ -0,0 +1,106 @@ +--- +title: About the retries attribute of the service object +content_type: support +description: How Kong's retry behavior works for service objects, including how to observe retries in debug logs. +products: + - gateway +works_on: + - on-prem + - konnect +tldr: + q: How do I check the behavior of the retries attribute? + a: | + When an upstream is unreachable, Kong retries the connection up to the configured number of times. You can observe this in debug logs. +faqs: + - q: Does the service object only retry when an upstream object is set? + a: No, the service object can retry requests even if an upstream object has not been set. + - q: Does the service object retry on HTTP 4xx/5xx responses? + a: No, retries happen only for TCP connection errors. However, {{site.base_gateway}} can perform HTTP and TCP health checks using the upstream object. For more details, see the Health Checks and Circuit Breakers documentation. +--- + +## How to check the behavior of the retries attribute + +1. Set `KONG_LOG_LEVEL=debug` and reload {{site.base_gateway}}. + + In your container, set `KONG_LOG_LEVEL` to `debug` + + ```bash + echo "KONG_LOG_LEVEL=debug kong reload exit" | docker exec -i kong-ee /bin/sh + ``` + +2. Run the httpbin container. + + ```bash + docker run -d --name httpbin --network=kong-ee-net -p 80:80 kong/httpbin + ``` + +3. Create a service object linked to the httpbin container, setting retries. + + ```bash + curl -i -X POST http://localhost:8001/services \ + --data name=example_service \ + --data url='http://httpbin/anything' \ + --data retries=5 + ``` + +4. Create a route object for the above service: + + ```bash + curl -i -X POST http://localhost:8001/services/example_service/routes \ + --data 'paths[]=/mock' \ + --data name=mocking + ``` + +5. Access the route successfully, receiving a 200 response: + + ```bash + curl localhost:8000/mock -i + + HTTP/1.1 200 OK + Content-Type: application/json + Content-Length: 406 + Connection: keep-alive + Server: gunicorn/19.9.0 + Date: Thu, 08 Apr 2021 06:44:09 GMT + Access-Control-Allow-Origin: * + Access-Control-Allow-Credentials: true + X-Kong-Upstream-Latency: 13 + X-Kong-Proxy-Latency: 4 + Via: kong/2.3.3.0-enterprise-edition + ... + ``` + +6. Stop the httpbin container, then access the route again: + + ```bash + docker stop httpbin + curl localhost:8000/mock -i + + HTTP/1.1 502 Bad Gateway + Server: openresty + Date: Thu, 08 Apr 2021 06:48:30 GMT + Content-Type: application/json; charset=utf-8 + Connection: keep-alive + Content-Length: 75 + X-Kong-Upstream-Latency: 3071 + X-Kong-Proxy-Latency: 30607 + Via: kong/2.3.3.0-enterprise-edition + + { + "message":"An invalid response was received from the upstream server" + } + ``` + + You can check the {{site.base_gateway}} logs to observe retry attempts, as shown below: + + ```bash + docker logs -f kong-ent + + DATE [debug] ... balancer(): setting address (try 1): xxx.xxx.xxx.xxx:xxx + ... + ... + DATE [error] ... connect() failed (110: Operation timed out) while connecting to upstream, client: xxx.xxx.xxx.xxx, server: kong, request: "GET /xxx HTTP/1.1", upstream: "xxx", host: "xxx" + DATE [debug] ... balancer(): setting address (try 2): xxx.xxx.xxx.xxx:xxx + ... + ... + ``` diff --git a/app/support.html b/app/support.html new file mode 100644 index 0000000000..bb56a20bb9 --- /dev/null +++ b/app/support.html @@ -0,0 +1,49 @@ +--- +title: Support Articles +layout: default +edit_and_issue_links: false +description: Browse troubleshooting guides and knowledge base articles for Kong products and services. +--- +
+
+
+
+

Support Articles

+ Browse troubleshooting guides and knowledge base articles for Kong products and services. +
+
+ +
+ +
+
diff --git a/docs/support/About-retries-attribute-of-service-object.md b/docs/support/About-retries-attribute-of-service-object.md deleted file mode 100644 index 846e53a1ff..0000000000 --- a/docs/support/About-retries-attribute-of-service-object.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -# REQUIRED: The title that appears at the top of the page -title: How to check the behavior of retries attribute? - -# REQUIRED: Must be set to "support" for support articles -content_type: support - - -# OPTIONAL: Which Kong products this article applies to -# Common values: gateway, konnect, mesh, insomnia, deck -products: - - gateway - -# REQUIRED for Gateway support articles (when products includes "gateway"); OPTIONAL otherwise -# accepted values: on-prem, konnect -works_on: - - on-prem - - konnect - - - -# OPTIONAL: TL;DR section that appears at the top of the article -# Provides a quick question and answer summary -tldr: - q: How do I check the behavior of the retries attribute? - a: | - When an upstream is unreachable, Kong retries the connection up to the configured number of times. You can observe this in debug logs. - ---- - -Please install Kong on Docker by following the official guide: Kong Docker Installation. - -**Step 1**: Set KONG_LOG_LEVEL=debug and reload Kong. - -In your container, set KONG_LOG_LEVEL to **debug** - -```bash -$ echo "KONG_LOG_LEVEL=debug kong reload exit" | docker exec -i kong-ee /bin/sh -``` - -**Step 2**: Run the httpbin container. - -```bash -$ docker run -d --name httpbin --network=kong-ee-net -p 80:80 kennethreitz/httpbin -``` - -**Step 3**: Create a service object linked to the httpbin container, setting retries - -```bash -$ curl -i -X POST http://localhost:8001/services \ - --data name=example_service \ - --data url='http://httpbin/anything' \ - --data retries=5 -``` - -**Step 4**: Create a route object for the above service: - -```bash -$ curl -i -X POST http://localhost:8001/services/example_service/routes \ - --data 'paths[]=/mock' \ - --data name=mocking -``` - -**Step 5**: Access the route successfully, receiving a 200 response: - -```bash -$ curl localhost:8000/mock -i - -HTTP/1.1 200 OK -Content-Type: application/json -Content-Length: 406 -Connection: keep-alive -Server: gunicorn/19.9.0 -Date: Thu, 08 Apr 2021 06:44:09 GMT -Access-Control-Allow-Origin: * -Access-Control-Allow-Credentials: true -X-Kong-Upstream-Latency: 13 -X-Kong-Proxy-Latency: 4 -Via: kong/2.3.3.0-enterprise-edition -... -``` - -**Step 6**: Stop the httpbin container, then access the route again: - -```bash -$ docker stop httpbin -$ curl localhost:8000/mock -i - -HTTP/1.1 502 Bad Gateway -Server: openresty -Date: Thu, 08 Apr 2021 06:48:30 GMT -Content-Type: application/json; charset=utf-8 -Connection: keep-alive -Content-Length: 75 -X-Kong-Upstream-Latency: 3071 -X-Kong-Proxy-Latency: 30607 -Via: kong/2.3.3.0-enterprise-edition - -{ - "message":"An invalid response was received from the upstream server" -} -``` - -You can check the Kong logs to observe retry attempts, as shown below: - -```bash -$ docker logs -f kong-ent - -DATE [debug] ... balancer(): setting address (try 1): xxx.xxx.xxx.xxx:xxx -... -... -DATE [error] ... connect() failed (110: Operation timed out) while connecting to upstream, client: xxx.xxx.xxx.xxx, server: kong, request: "GET /xxx HTTP/1.1", upstream: "xxx", host: "xxx" -DATE [debug] ... balancer(): setting address (try 2): xxx.xxx.xxx.xxx:xxx -... -... -``` - -faqs: - - q: Does the service object only retry when an upstream object is set? - a: No, the service object can retry requests even if an upstream object has not been set. - - - q: Does the service object retry on HTTP 4xx/5xx responses? - a: No, retries happen only for TCP connection errors. However, Kong can perform HTTP and TCP health checks using the upstream object. For more details, see the Health Checks and Circuit Breakers documentation. - From 2b05e6468e90882c13fcb922d1f58e745a351230 Mon Sep 17 00:00:00 2001 From: Angel Date: Tue, 21 Apr 2026 16:29:37 -0400 Subject: [PATCH 10/10] Delete app/support.html --- app/support.html | 49 ------------------------------------------------ 1 file changed, 49 deletions(-) delete mode 100644 app/support.html diff --git a/app/support.html b/app/support.html deleted file mode 100644 index bb56a20bb9..0000000000 --- a/app/support.html +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: Support Articles -layout: default -edit_and_issue_links: false -description: Browse troubleshooting guides and knowledge base articles for Kong products and services. ---- -
-
-
-
-

Support Articles

- Browse troubleshooting guides and knowledge base articles for Kong products and services. -
-
- -
- -
-