A route config is already verify flexible in that it allows for matching on incoming request headers and the ability to add custom request headers or override request headers with custom values.

In our case, we'd like to also match on the connecting IP or ASN, so that we can adjust set a customer header only when all of these are true:

1. connecting ASN is match

2. request header value is a match

When this matches we want to add a customer header with custom value and then route. This doesn't seem to be posible with service policy chaining and even it if is, allowing for ASN or IP set/range match directly in the single page route config is far less complex for the human setting up the config.

AdjustingClient...

×

Attachments Open full size