A customer pointed out that following items should be clarified in 4.1.6. Camel Service and Chapter 6. Transforming 3scale API Management message content using policy extensions in Fuse

• Settings in Camel Service Policy doesn't accept https schema.
• When the schema of a request to API Backend is http, APIcast uses the http_proxy value ( or all_proxy if http_proxy isn't defined) to connect Camel proxy. Such http requests cannot be encrypted using TLS. The port number to be set for http_proxy(all_proxy) must be a port that Camel accepts HTTP.
• When the schema of a request to API Backend is https, APIcast uses the https_proxy value ( or all_proxy if https_proxy isn't defined) to connect Camel proxy. Such https requests are encrypted using TLS. The port number to be set for https_proxy(all_proxy) must be a port that Camel accepts HTTPS.
• Camel Service Policy doens't use CONNECT method.
• When HTTP_PROXY, HTTPS_PROXY, ALL_PROXY are set as APIcast's environment variables, APIcast connects API Backends via a proxy server. In this case, APIcast uses CONNECT method.