From f8bb1a84e22338f16cb3e8e545a2e1a929cd0053 Mon Sep 17 00:00:00 2001 From: Ryan Baxter Date: Wed, 6 Nov 2019 10:18:25 -0500 Subject: [PATCH] Formatting docs based on feedback --- docs/src/main/asciidoc/spring-cloud-gateway.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/src/main/asciidoc/spring-cloud-gateway.adoc b/docs/src/main/asciidoc/spring-cloud-gateway.adoc index 609f3521..6f508f0c 100644 --- a/docs/src/main/asciidoc/spring-cloud-gateway.adoc +++ b/docs/src/main/asciidoc/spring-cloud-gateway.adoc @@ -599,15 +599,15 @@ spring: - id: circuitbreaker_route uri: lb://backing-service:8088 predicates: - - Path=/consumingserviceendpoint + - Path=/consumingServiceEndpoint filters: - name: CircuitBreaker args: name: myCircuitBreaker - fallbackUri: forward:/incaseoffailureusethis - - RewritePath=/consumingserviceendpoint, /backingserviceendpoint + fallbackUri: forward:/inCaseOfFailureUseThis + - RewritePath=/consumingServiceEndpoint, /backingServiceEndpoint ---- -This will forward to the `/incaseoffailureusethis` URI when the circuit breaker fallback is called. Note that this example also demonstrates (optional) Spring Cloud Netflix Ribbon load-balancing via the `lb` prefix on the destination URI. +This will forward to the `/inCaseofFailureUseThis` URI when the circuit breaker fallback is called. Note that this example also demonstrates (optional) Spring Cloud Netflix Ribbon load-balancing via the `lb` prefix on the destination URI. The primary scenario is to use the `fallbackUri` to an internal controller or handler within the gateway app. However, it is also possible to reroute the request to a controller or handler in an external application, like so: