You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/root/start/sandboxes/cache.rst
+5-5
Original file line number
Diff line number
Diff line change
@@ -8,9 +8,9 @@ In this example, we demonstrate how HTTP caching can be utilized in Envoy by usi
8
8
The setup of this sandbox is based on the setup of the :ref:`Front Proxy sandbox <install_sandboxes_front_proxy>`.
9
9
10
10
All incoming requests are routed via the front Envoy, which acts as a reverse proxy sitting on
11
-
the edge of the ``envoymesh`` network. Ports ``8000`` and ``8001`` are exposed by docker
11
+
the edge of the ``envoymesh`` network. Port ``8000`` is exposed by docker
12
12
compose (see :repo:`/examples/cache/docker-compose.yaml`) to handle ``HTTP`` calls
13
-
to the services, and requests to ``/admin`` respectively. Two backend services are deployed behind the front Envoy, each with a sidecar Envoy.
13
+
to the services. Two backend services are deployed behind the front Envoy, each with a sidecar Envoy.
14
14
15
15
The front Envoy is configured to run the Cache Filter, which stores cacheable responses in an in-memory cache,
16
16
and serves it to subsequent requests. In this demo, the responses that are served by the deployed services are stored in :repo:`/examples/cache/responses.yaml`.
@@ -35,9 +35,9 @@ Step 3: Start all of our containers
0 commit comments