From 3025134b938797c30cb1f7f0255f56f2c073d5a2 Mon Sep 17 00:00:00 2001 From: Spencer Gibb Date: Wed, 23 Aug 2017 15:43:12 -0600 Subject: [PATCH] diagram --- docs/src/main/asciidoc/images/.gitkeep | 0 ...m.png => spring_cloud_gateway_diagram.png} | Bin 27306 -> 27306 bytes .../main/asciidoc/spring-cloud-gateway.adoc | 2 +- 3 files changed, 1 insertion(+), 1 deletion(-) delete mode 100644 docs/src/main/asciidoc/images/.gitkeep rename docs/src/main/asciidoc/images/{gateway_diagram.png => spring_cloud_gateway_diagram.png} (99%) diff --git a/docs/src/main/asciidoc/images/.gitkeep b/docs/src/main/asciidoc/images/.gitkeep deleted file mode 100644 index e69de29b..00000000 diff --git a/docs/src/main/asciidoc/images/gateway_diagram.png b/docs/src/main/asciidoc/images/spring_cloud_gateway_diagram.png similarity index 99% rename from docs/src/main/asciidoc/images/gateway_diagram.png rename to docs/src/main/asciidoc/images/spring_cloud_gateway_diagram.png index a288c470a221386dc70ca0edbabf2b62d212ea4f..25ffbcce890c14a40896adb7c77ecab31d0b7f19 100644 GIT binary patch delta 26 icmZ2=m2uTo#tmS^hJ0`sQL5^E3dVUJGOZ delta 26 icmZ2=m2uTo#tmY3i76xw)9dJPiPxaSFEp diff --git a/docs/src/main/asciidoc/spring-cloud-gateway.adoc b/docs/src/main/asciidoc/spring-cloud-gateway.adoc index d11ef8c0..041ee45b 100644 --- a/docs/src/main/asciidoc/spring-cloud-gateway.adoc +++ b/docs/src/main/asciidoc/spring-cloud-gateway.adoc @@ -30,7 +30,7 @@ If you include the starter, but, for some reason, you do not want the gateway to [[gateway-how-it-works]] == How It Works -image::{imagesurl}/gateway_diagram.png[Spring Cloud Gateway Diagram] +image::{imagesurl}/spring_cloud_gateway_diagram.png[Spring Cloud Gateway Diagram] Clients make requests to Spring Cloud Gateway. If the Gateway Handler Mapping determines that a request matches a Route, it is sent to the Gateway Web Handler. This handler runs sends the request through a filter chain that is specific to the request. The reason the filters are divided by the dotted line, is that filters may execute logic before the proxy request is sent or after. All "pre" filter logic is executed, then the proxy request is made. After the proxy request is made, the "post" filter logic is executed.