Los proxies de reenvío proporcionan un único punto a través del cual varias máquinas envían solicitudes a un servidor externo. Pueden aplicar políticas de seguridad, registrar y analizar solicitudes, y realizar otras acciones para que las solicitudes cumplan las reglas de tu empresa. Con Apigee hybrid, puedes configurar un proxy de reenvío que medie entre tus proxies de API y un TargetEndpoint externo (un servidor de destino de backend).
Para usar un proxy de reenvío HTTP entre el entorno híbrido y TargetEndpoint, debes configurar los ajustes del proxy saliente en el archivo de anulaciones. Estas propiedades de ámbito de entorno
dirigen las solicitudes de destino de híbrido al proxy de reenvío HTTP. También debe asegurarse de que use.proxy esté definido como "true" en cualquier TargetEndpoint que quiera que pase por un proxy de reenvío HTTP. Consulta las instrucciones en la parte inferior de la página.
Para configurar un entorno híbrido para el reenvío de proxy, añada la propiedad envs.httpProxy al archivo de anulaciones y aplíquela al clúster. Por ejemplo:
El proxy de reenvío se configura para un entorno. Todo el tráfico que va de los proxies de API de ese entorno a los destinos de backend pasa por el proxy de reenvío HTTP especificado. Si el tráfico de un destino específico de un proxy de API debe ir directamente al destino de backend, sin pasar por el proxy de reenvío, defina la siguiente propiedad en TargetEndpoint para anular el proxy de reenvío HTTP:
<Property name="use.proxy">false</Property>
Para obtener más información sobre cómo definir las propiedades de TargetEndpoint, incluido cómo configurar la conexión al endpoint de destino, consulta la referencia de propiedades de Endpoint.
Asigna el valor "true" a use.proxy en cualquier TargetEndpoint que quieras que pase por un proxy de reenvío HTTP:
[[["Es fácil de entender","easyToUnderstand","thumb-up"],["Me ofreció una solución al problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Es difícil de entender","hardToUnderstand","thumb-down"],["La información o el código de muestra no son correctos","incorrectInformationOrSampleCode","thumb-down"],["Me faltan las muestras o la información que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-04 (UTC)."],[[["\u003cp\u003eThis document details how to configure a forward proxy for Apigee hybrid installations, which acts as an intermediary for API proxies and external TargetEndpoints.\u003c/p\u003e\n"],["\u003cp\u003eTo enable a forward proxy, you must configure outbound proxy settings in your overrides file by adding the \u003ccode\u003eenvs.httpProxy\u003c/code\u003e property and applying it to the cluster, ensuring the scheme is set to HTTP in uppercase.\u003c/p\u003e\n"],["\u003cp\u003eForward proxying is environment-specific, directing all traffic from API proxies to backend targets through the specified HTTP forward proxy.\u003c/p\u003e\n"],["\u003cp\u003eYou can bypass the forward proxy for specific targets by setting the \u003ccode\u003euse.proxy\u003c/code\u003e property to "false" within the TargetEndpoint configuration.\u003c/p\u003e\n"],["\u003cp\u003eTo route a specific TargetEndpoint through the forward proxy, set the \u003ccode\u003euse.proxy\u003c/code\u003e property to "true" within the endpoint's configuration.\u003c/p\u003e\n"]]],[],null,["# Configure forward proxying for API proxies\n\n| You are currently viewing version 1.10 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| **Important:** Apigee also supports a [forward proxy functionality for non-hybrid\n| installations](/apigee/docs/api-platform/fundamentals/environments-overview#forward-proxy). Use the instructions provided on this page to configure forward proxies for hybrid rather than the general Apigee functionality.\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.10/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` must be HTTP 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.10/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```"]]
