Proxy forward menyediakan satu titik yang digunakan beberapa mesin untuk mengirim permintaan ke
server eksternal. Aturan ini dapat menerapkan kebijakan keamanan, mencatat dan menganalisis permintaan, serta melakukan tindakan
lainnya agar permintaan mematuhi aturan bisnis Anda.
Dengan menggunakan forward proxy di Apigee hybrid,
Anda dapat mencegat dan mengelola semua traffic keluar dari cluster Kubernetes. Hal ini mencakup permintaan proxy API ke Endpoint Target dan komunikasi dengan *.googleapis.com yang dibuat runtime hibrida untuk pipeline debug dan analisisnya serta untuk kebijakan seperti MessageLogging.
Untuk menggunakan proxy penerusan HTTP antara hybrid dan TargetEndpoint, Anda harus mengonfigurasi setelan proxy keluar di file penggantian. Properti cakupan lingkungan ini
merutekan permintaan target dari hybrid ke proxy penerusan HTTP. Anda juga perlu memastikan
use.proxy disetel ke "true" untuk TargetEndpoint yang ingin Anda teruskan melalui proxy
penerusan HTTP. Lihat bagian bawah halaman untuk mengetahui petunjuknya.
Untuk mengonfigurasi lingkungan campuran guna meneruskan proxy, tambahkan properti envs.httpProxy ke file penggantian dan terapkan ke cluster. Contoh:
Penerusan proxy dikonfigurasi untuk lingkungan; semua traffic yang berasal dari proxy API di lingkungan tersebut ke target backend akan melalui proxy penerusan HTTP yang ditentukan. Jika traffic untuk
target proxy API tertentu harus langsung diarahkan ke target backend, dengan mengabaikan proxy
penerusan, tetapkan properti berikut di TargetEndpoint untuk mengganti proxy penerusan
HTTP:
<Property name="use.proxy">false</Property>
Untuk mengetahui informasi selengkapnya tentang cara menetapkan properti TargetEndpoint, termasuk cara mengonfigurasi koneksi ke endpoint target, lihat Referensi properti endpoint.
Tetapkan use.proxy ke "true" untuk TargetEndpoint yang ingin Anda teruskan melalui
proxy penerusan HTTP:
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 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."]]
