Header-based routing directs requests to a tagged application revision through an HTTP header rather than a separate revision URL. It supports A/B testing and lets developers reach debugging or experimental versions while keeping the normal service URL unchanged. section 8.2.2
A Knative Serving workflow uses these steps:
- Create traffic rules that assign a tag, such as version110, to the target revision while leaving normal traffic on the service’s existing route. section 8.2.2
- Send requests with the designated HTTP header containing the tag name; use a browser extension such as ModHeader when testing from a browser. section 8.2.2
Targeting version110
Keep the standard Knative Service URL for ordinary requests, then configure a request header whose value identifies the version110 tag. Requests carrying that header reach the tagged revision, allowing developers to test the debugging version without changing the public URL. section 8.2.2
