anchor.diff:  
   For example, external HTTP/1.1 requests are forwarded to your app over HTTP/2.
   Your app does not have the opportunity to negotiate what protocol it receives.
  -Apps receive HTTP/2
   
   <p class="note"><strong>Note:</strong>
   If a client is familiar with the HTTP/2 specification,
  
positive.code: For more information, see <a href="https://datatracker.ietf.org/doc/html/rfc7540#section-3.4">Starting HTTP/2 with Prior Knowledge</a> in
  <em>RFC 7540: Hypertext Transfer Protocol Version 2 (HTTP/2)</em>.</p>
  
  There are multiple ways to configure end-to-end HTTP/2 for your app.
  
  See the following sections:
  
  - [Configure End-to-End HTTP/2 Using the App Manifest](#e2e-manifest)
  
  ### <a id="e2e-manifest"></a> Configure End-to-End HTTP/2 Using the App Manifest
  
  To configure end-to-end HTTP/2 using the app manifest:
  
  1. Acquire an application that supports serving HTTP/2 traffic with prior knowledge.
  For this example, we will use [the HTTP/2 test app from Cloud Foundry Acceptance Tests](https://github.com/cloudfoundry/cf-acceptance-tests/tree/http2_routing/assets/http2).
  
  1. Create an application manifest, `manifest.yml`, with a route mapped to the application with HTTP/2:
  
  	```yaml
  	---
  	applications:
  	- name: my-app
  	  routes:
  	    - route: my-app.example.com
  	      protocol: http2
  	```
  
  1. Push the application with the manifest:
  
  	```
  	cf push -f manifest.yml
  	```
  
  1. Issue a HTTP/2 request to the application:
  
  	```
  	curl my-app.example.com --http2 -v
  	```
  
  1. Note that the request and response are issued over HTTP/2.
  
  1. The response from the test application will include the request's protocol.
  Note that it recieved the request over HTTP/2:
  
  	```
  	Hello, /, TLS: false, Protocol: HTTP/2.0
  	```
  
  #### <a id="example-3"></a> Example 3: End-to-End HTTP/2 Using CLI
  
  1. Acquire an application that supports serving HTTP/2 traffic with prior knowledge.
  For this example, we will use [the HTTP/2 test app from Cloud Foundry Acceptance Tests](https://github.com/cloudfoundry/cf-acceptance-tests/tree/http2_routing/assets/http2).
  
  1. Push the application without a default route:
  
  	```
  	cf push --no-route
  	```
  
  1. Map a route with destination protocol `http2`:
  
  	```
  	cf map-route my-app example.com --hostname host --destination-protocol http2
  	```
  
  1. Issue a HTTP/2 request to the application:
  
  	```
  	curl host.example.com --http2 -v
  	```
  
  1. Note that the request and response are issued over HTTP/2.
  
  1. The response from the test application will include the request's protocol.
  Note that it recieved the request over HTTP/2:
  
  	```
  	Hello, /, TLS: false, Protocol: HTTP/2.0
  	```
  
  #### <a id="example-4"></a> Example 4: Pushing a gRPC Application
  
  1. Acquire an application that supports serving gRPC traffic.
  For this example, we will use [the gRPC test app from Cloud Foundry Acceptance Tests](https://github.com/cloudfoundry/cf-acceptance-tests/tree/http2_routing/assets/grpc).
  
  1. Push the app with HTTP/2 enabled using one of the methods described above.
  
  1. Issues a gRPC request to the application using [grpcurl](https://github.com/fullstorydev/grpcurl):
  
  	```
  	grpcurl -vv -import-path ./test/ -proto test.proto my-app.example.com:443 test.Test.Run
  	```
  
  1. Note that the gRPC request succeeds:
  
  	```
  	Response contents:
  
negative.code: 	  "body": "Hello"
  	}
  	```
  