I proxy in avanti forniscono un unico punto tramite il quale piรน macchine inviano richieste a un
server esterno. Possono applicare criteri di sicurezza, registrare e analizzare le richieste ed eseguire altre azioni in modo che le richieste rispettino le tue regole aziendali. Con Apigee Hybrid, puoi configurare un proxy in avanti che intermedi i proxy API e un TargetEndpoint esterno (un server di destinazione di backend).
Per utilizzare un proxy in avanti HTTP tra l'istanza ibrida e TargetEndpoint, devi configurare le impostazioni del proxy in uscita nel file delle sostituzioni. Queste proprietร basate sull'ambiente indirizzano le richieste di destinazione dall'ambiente ibrido al proxy di inoltro HTTP. Inoltre, devi assicurarti che use.proxy sia impostato su "true" per qualsiasi TargetEndpoint che vuoi inoltrare tramite un proxy forward HTTP. Leggi le istruzioni in fondo alla pagina.
Per configurare un ambiente ibrido per il proxy di inoltro, aggiungi la proprietร envs.httpProxy al file delle sostituzioni e applicala al cluster. Ad esempio:
Il proxy in avanti รจ configurato per un ambiente; tutto il traffico che passa dai proxy API in quell'ambiente ai target di backend passa attraverso il proxy in avanti HTTP specificato. Se il traffico per un
target specifico di un proxy API deve andare direttamente al target di backend, bypassando il proxy forward, imposta la seguente proprietร in TargetEndpoint per eseguire l'override del proxy forward HTTP:
<Property name="use.proxy">false</Property>
Per ulteriori informazioni sull'impostazione delle proprietร TargetEndpoint, inclusa la configurazione della connessione all'endpoint di destinazione, consulta Riferimento per le proprietร degli endpoint.
Imposta use.proxy su "true" per qualsiasi TargetEndpoint per cui vuoi passare tramite un proxy di inoltro HTTP:
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema รจ stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-03 UTC."],[[["\u003cp\u003eThis documentation covers version 1.7 of Apigee hybrid, which is end-of-life, and users should upgrade to a newer version.\u003c/p\u003e\n"],["\u003cp\u003eApigee hybrid can be configured to use a forward proxy, which acts as an intermediary between API proxies and external target servers for enforcing security and logging requests.\u003c/p\u003e\n"],["\u003cp\u003eConfiguring an HTTP forward proxy in Apigee hybrid requires setting the \u003ccode\u003eenvs.httpProxy\u003c/code\u003e property in the overrides file with the scheme, host, and port.\u003c/p\u003e\n"],["\u003cp\u003eBy default, all traffic from API proxies within a configured environment will go through the forward proxy, but this can be overridden on a per-target basis by setting the \u003ccode\u003euse.proxy\u003c/code\u003e property to "false" in the TargetEndpoint.\u003c/p\u003e\n"],["\u003cp\u003eSetting \u003ccode\u003euse.proxy\u003c/code\u003e to "true" in a TargetEndpoint ensures that traffic to that target will go through the configured HTTP forward proxy.\u003c/p\u003e\n"]]],[],null,["# Configure forward proxying for API proxies\n\n| You are currently viewing version 1.7 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.7/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.7/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```"]]
