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.
Utilizzando un proxy inoltrante in Apigee hybrid,
puoi intercettare e gestire tutto il traffico in uscita dal tuo cluster Kubernetes. Sono incluse le richieste proxy dell'API agli endpoint target e la comunicazione con *.googleapis.com che il runtime ibrido effettua per la pipeline di debug e analisi e per criteri come MessageLogging.
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-04 UTC."],[[["\u003cp\u003eForward proxies allow multiple machines to send requests to an external server through a single point, enabling security policy enforcement, request logging, and analysis.\u003c/p\u003e\n"],["\u003cp\u003eApigee hybrid allows configuration of a forward proxy that sits between API proxies and an external TargetEndpoint, with specific instructions for hybrid setups, which differ from general Apigee functionality.\u003c/p\u003e\n"],["\u003cp\u003eTo use an HTTP forward proxy in Apigee hybrid, configure the \u003ccode\u003eenvs.httpProxy\u003c/code\u003e property in your overrides file with the proxy's scheme, host, and port, ensuring the scheme is HTTP and in uppercase.\u003c/p\u003e\n"],["\u003cp\u003eForward proxying in Apigee hybrid is environment-specific, and all traffic from API proxies in that environment to backend targets goes through it, unless the \u003ccode\u003euse.proxy\u003c/code\u003e property is set to "false" within a specific TargetEndpoint.\u003c/p\u003e\n"],["\u003cp\u003eTo direct traffic through the HTTP forward proxy for a particular TargetEndpoint, the \u003ccode\u003euse.proxy\u003c/code\u003e property must be set to "true" in the TargetEndpoint configuration.\u003c/p\u003e\n"]]],[],null,["# Configure forward proxying for API proxies\n\n| You are currently viewing version 1.14 of the Apigee hybrid documentation. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n| **Note:** Both Apigee and Apigee hybrid supporta [forward proxy functionality](/apigee/docs/api-platform/fundamentals/environments-overview#forward-proxy). Use the instructions on this page to configure forward proxies for hybrid rather than the general Apigee functionality.\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.\n\nUsing a forward proxy in Apigee hybrid,\nyou can intercept and manage all egress traffic from your Kubernetes cluster. This includes API\nproxy requests to Target Endpoints and communication with `*.googleapis.com` that the hybrid\nruntime makes for its debug and analytics pipeline and for policies like [MessageLogging](/apigee/docs/api-platform/reference/policies/message-logging-policy).\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.14/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.14/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```\n| **Important note on external calls:** Configuring non-API proxy forwarding using [`httpProxy`](/apigee/docs/hybrid/v1.14/config-prop-ref#httpproxy) without also setting [`envs.httpProxy`](/apigee/docs/hybrid/v1.14/config-prop-ref#envs) will not apply the proxy configuration to Apigee Runtime's external calls to services like Pub/Sub or other Google Cloud APIs.\n|\n|\n| If you only specify `httpProxy`, you must also ensure that `*.googleapis.com` is allowlisted for your Apigee Runtime pods to enable connectivity to these services."]]
