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 Apigee hybrid, Anda dapat mengonfigurasi proxy forward
yang menjadi perantara proxy API dan TargetEndpoint eksternal (server target backend).
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-08-19 UTC."],[[["\u003cp\u003eThis documentation covers version 1.2 of Apigee hybrid, which is now end-of-life and requires an 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 for requests from API proxies to external TargetEndpoints, enabling security policy enforcement and request logging.\u003c/p\u003e\n"],["\u003cp\u003eConfiguring a forward proxy involves setting outbound proxy properties in the overrides file, specifically using the \u003ccode\u003eenvs.httpProxy\u003c/code\u003e property, along with setting the scheme, host, and port of the proxy.\u003c/p\u003e\n"],["\u003cp\u003eForward proxying is environment-specific, so all traffic from API proxies within that environment to backend targets will use the specified proxy unless the \u003ccode\u003euse.proxy\u003c/code\u003e property is explicitly set to "false" in the TargetEndpoint.\u003c/p\u003e\n"],["\u003cp\u003eTo make a specific TargetEndpoint utilize the forward proxy, the \u003ccode\u003euse.proxy\u003c/code\u003e property within that TargetEndpoint must be set to "true".\u003c/p\u003e\n"]]],[],null,["# Configure forward proxying for API proxies\n\n| You are currently viewing version 1.2 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.2/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.2/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```"]]
