It's not clear that 3scale is populating the HTTP_SCHEME, HTTP_HOST, HTTP_PORT, HTTP_PATH variables in the Apache Camel route based on the configuration of the 3scale API backend. These and any other Apache Camel route variables that are automatically populated as part of the proxy policy usage in a 3scale policy chain need to be called out specifically and clearly in the documentation.

Reported by: mhockelb

https://access.redhat.com/documentation/en-us/red_hat_3scale_api_management/2.7/html/administering_the_api_gateway/transform-with-policy-extension#annotations:31a322d5-2776-46ee-ab2d-241b664e2150