diff --git a/labapp/app/markdown/manipulation.md b/labapp/app/markdown/manipulation.md index d15513d..521f91d 100644 --- a/labapp/app/markdown/manipulation.md +++ b/labapp/app/markdown/manipulation.md @@ -6,12 +6,11 @@
-Since web traffic has been traversing proxies, engineers have needed to alter HTTP content for increased observability ([XFF](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For)), performance ([cache-control](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control)), or other reasons ([JWT](https://en.wikipedia.org/wiki/JSON_Web_Token)). +Since web traffic has been traversing proxies, engineers have needed to alter HTTP content for increased observability (XFF), performance (Cache-Control), or core functionality (JWT). "Proxy Pass" functionality has been part of web servers since the early Apache days. Adding, removing, and altering Headers are tablestakes for ADCs, CDNs, and software-based load balancers. F5 XC App Connect enables this functionality granularly on routes or broadly on the load balancer. -
### **Exercise 1: Path Rewrite** @@ -55,7 +54,7 @@ document.getElementById('requestBtn1').addEventListener('click', () => { }); -Since questions on this functionality are often asked on F5 DevCentral, a hint might be warranted. +Questions on this functionality are often asked on F5 DevCentral. Here's a hint.

@@ -86,11 +85,11 @@ Use the

  •     - Insert a request header named X-MCN-src-site to identifies the UDF CE to the origin. Do not use a static value. + Insert a request header named X-MCN-src-site to identify the UDF CE to the origin. Do not use a static value.
  •     - Insert a request header named X-MCN-namespace to identifies the ephemeral namespace to the origin. Do not use a static value. + Insert a request header named X-MCN-namespace to identify the ephemeral namespace to the origin. Do not use a static value.
    • @@ -139,9 +138,9 @@ document.getElementById('requestBtn2').addEventListener('click', () => { #### **Test Criteria** -
    - -This test will evaluate response headers. + ```http GET https://eph-ns.mcn-lab.f5demos.com/aws HTTP/1.1 diff --git a/labapp/app/markdown/overview.md b/labapp/app/markdown/overview.md index 77a2ca4..dd78fde 100644 --- a/labapp/app/markdown/overview.md +++ b/labapp/app/markdown/overview.md @@ -80,7 +80,7 @@ To complete lab exercises, you will run tests against the load balancer advertis You will build this load balancer in the     first exercise. All tests will be run from this lab app. -Each test will specify success criteria immediately prior to the button. +Each test will specify success criteria immediately before to the button. Here are some examples to try. diff --git a/labapp/app/markdown/portability.md b/labapp/app/markdown/portability.md index af61565..965b172 100644 --- a/labapp/app/markdown/portability.md +++ b/labapp/app/markdown/portability.md @@ -11,7 +11,7 @@ The configuration built so far handles load balancing, routing, and content mani XC refers to this object as a "load balancer" -- but it's really the holistic representation of an application whose service endpoints live across the distributed network. The object is simple -- it doesn't yet include configuration for WAAP, API protection, or a service policy. -What seperate XC from traditional ADCs is the flexibility of defining where the object is advertised. +What seperates XC from traditional ADCs is flexibility in defining where a load balancer is advertised.
    @@ -67,9 +67,14 @@ document.getElementById('requestBtn1').addEventListener('click', () => { ### **Exercise 2: Find a Friend** -Do you have a friend working on the lab? -Ask them their ephemeral namespace to test advertisement from the UDF site (or test with the value already populated). +Do you have a friend working on the lab? Find thier ephemeral namespace (or use the one provided). +
    diff --git a/labapp/app/markdown/route.md b/labapp/app/markdown/route.md index 29830a3..65545c9 100644 --- a/labapp/app/markdown/route.md +++ b/labapp/app/markdown/route.md @@ -8,7 +8,7 @@ Modern applications, and some classic ones, are often comprised of disparate services spread across sites. MCN solutions must be able to make routing decisions based on characterstics of an HTTP request. -F5 XC App Connect is a distributed L7 proxy that provide intelligent routing, visibility, and strategic points of control. +F5 XC App Connect is a distributed L7 proxy that provides intelligent routing, visibility, and strategic points of control.
    @@ -19,15 +19,15 @@ Build routing rules and configure your load balancer to route traffic between th @@ -77,11 +77,11 @@ Build rules to route traffic between the two cloud apps based on an arbitrary HT