Os proxies de encaminhamento fornecem um único ponto através do qual várias máquinas enviam pedidos para um servidor externo. Podem aplicar políticas de segurança, registar e analisar pedidos, e realizar outras ações para que os pedidos cumpram as regras da sua empresa. Com o Apigee hybrid, pode configurar um proxy de encaminhamento que intermedeia os seus proxies de API e um TargetEndpoint externo (um servidor de destino de back-end).
Para usar um proxy de encaminhamento HTTP entre o híbrido e o TargetEndpoint, tem de configurar as definições de proxy de saída no ficheiro de substituições. Estas propriedades ao nível do ambiente
encaminham pedidos de destino do híbrido para o proxy de encaminhamento HTTP. Também tem de garantir que use.proxy está definido como "true" para qualquer TargetEndpoint que queira passar por um proxy de encaminhamento HTTP. Consulte a parte inferior da página para ver instruções.
O proxying de encaminhamento está configurado para um ambiente. Todo o tráfego que passa por proxies de API nesse ambiente para alvos de back-end passa pelo proxy de encaminhamento HTTP especificado. Se o tráfego para um destino específico de um proxy de API deve ir diretamente para o destino de back-end, ignorando o proxy de encaminhamento, defina a seguinte propriedade no TargetEndpoint para substituir o proxy de encaminhamento HTTP:
<Property name="use.proxy">false</Property>
Para mais informações sobre a definição das propriedades TargetEndpoint, incluindo como configurar a ligação ao ponto final de destino, consulte a referência de propriedades do ponto final.
Defina use.proxy como "true" para qualquer TargetEndpoint que queira passar por
um proxy de encaminhamento HTTP:
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-09-03 UTC."],[[["\u003cp\u003eThis documentation version (1.6) for Apigee hybrid is end-of-life and an upgrade to a newer version is required.\u003c/p\u003e\n"],["\u003cp\u003eApigee hybrid can be configured to use a forward proxy, a single point for multiple machines to send requests to external servers, allowing for security policy enforcement and request analysis.\u003c/p\u003e\n"],["\u003cp\u003eConfiguring an HTTP forward proxy involves setting the \u003ccode\u003eenvs.httpProxy\u003c/code\u003e property in the overrides file and ensuring \u003ccode\u003euse.proxy\u003c/code\u003e is set to "true" in the TargetEndpoint for traffic that should go through the proxy.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003escheme\u003c/code\u003e property for the forward proxy must be either HTTP or HTTPS and specified in uppercase.\u003c/p\u003e\n"],["\u003cp\u003eTo bypass the forward proxy for a specific target, set the \u003ccode\u003euse.proxy\u003c/code\u003e property to "false" in the corresponding TargetEndpoint.\u003c/p\u003e\n"]]],[],null,["# Configure forward proxying for API proxies\n\n| You are currently viewing version 1.6 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nForward proxies provide a single point through which multiple machines send requests to an\nexternal server. They can enforce security policies, log and analyze requests, and perform other\nactions so that requests adhere to your business rules. With Apigee hybrid, you can configure a forward proxy\nthat intermediates your API proxies and an external TargetEndpoint (a backend target server).\n\nTo use an HTTP forward proxy between hybrid and the TargetEndpoint, you must configure\nthe outbound proxy settings in your overrides file. These environment-scoped properties\nroute target requests from hybrid to the HTTP forward proxy. You also need to ensure\n`use.proxy` is set to \"true\" for any TargetEndpoint that you want to go through an HTTP\nforward proxy. See the bottom of the page for instructions.\n\nTo configure a hybrid environment for forwarding proxying, add\nthe [`envs.httpProxy` property](/apigee/docs/hybrid/v1.6/config-prop-ref#envs) to your overrides file and apply it to the\ncluster. For example: \n\n```text\nenvs:\n - name: test\n httpProxy:\n scheme: HTTP\n host: 10.12.0.47\n port: 3128\n ...\n```\n| **NOTE:** The `scheme` can be HTTP or HTTPS and must be uppercase.\n\nFor details on each of the `envs.httpProxy` configuration properties refer to the\n[Configuration property reference](/apigee/docs/hybrid/v1.6/config-prop-ref#envs).\n\nForward proxying is configured for an environment; all traffic going from API\nproxies in that environment to backend targets goes through the specified HTTP\nforward proxy. If the traffic for a\nspecific target of an API proxy should go directly to the backend target, bypassing the forward\nproxy, then set the following property in the TargetEndpoint to override the HTTP forward\nproxy: \n\n```text\n\u003cProperty name=\"use.proxy\"\u003efalse\u003c/Property\u003e\n```\n\nFor more information on setting the TargetEndpoint properties, including how to configure\nthe connection to the target endpoint, see [Endpoint properties reference](/apigee/docs/api-platform/reference/endpoint-properties-reference).\n\nSet `use.proxy` to \"true\" for any TargetEndpoint that you want to go through\nan HTTP forward proxy: \n\n```text\n\u003cProperty name=\"use.proxy\"\u003etrue\u003c/Property\u003e\n```"]]
