When a product is using multiple backend, system still injects the old api_backend attribute into the proxy configuration. This causes the gateway to use the value set to that attribute as default endpoint whenever no backend path matches and catch-all mapping rule is present. Nonetheless, the value of the attribute cannot be edited.

The proposal is to nullify the old attribute when APIAP routing policy is present, case of at least one non-null backend path present.