You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| API threat detection with [Defender for APIs](protect-with-defender-for-apis.md)| ✔️ | ✔️ | ❌ | ❌ | ❌ |
90
90
91
91
<sup>1</sup> Depends on how the gateway is deployed, but is the responsibility of the customer.<br/>
92
92
<sup>2</sup> Connectivity to the self-hosted gateway v2 [configuration endpoint](self-hosted-gateway-overview.md#fqdn-dependencies) requires DNS resolution of the endpoint hostname.<br/>
93
-
<sup>3</sup> Two zones are enabled by default; not configurable.<br/>
94
-
<sup>4</sup> CA root certificates for self-hosted gateway are managed separately per gateway<br/>
95
-
<sup>5</sup> Client protocol needs to be enabled.
93
+
<sup>3</sup> CA root certificates for self-hosted gateway are managed separately per gateway<br/>
94
+
<sup>4</sup> Client protocol needs to be enabled.<br/>
95
+
<sup>5</sup> Configure using the [forward-request](forward-request-policy.md) policy.
Copy file name to clipboardExpand all lines: articles/api-management/forward-request-policy.md
+9-4Lines changed: 9 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ The `forward-request` policy forwards the incoming request to the backend servic
35
35
| timeout | The amount of time in seconds to wait for the HTTP response headers to be returned by the backend service before a timeout error is raised. Minimum value is 0 seconds. Values greater than 240 seconds may not be honored, because the underlying network infrastructure can drop idle connections after this time. Policy expressions are allowed. You can specify either `timeout` or `timeout-ms` but not both. | No | 300 |
36
36
| timeout-ms | The amount of time in milliseconds to wait for the HTTP response headers to be returned by the backend service before a timeout error is raised. Minimum value is 0 ms. Policy expressions are allowed. You can specify either `timeout` or `timeout-ms` but not both. | No | N/A |
37
37
| continue-timeout | The amount of time in seconds to wait for a `100 Continue` status code to be returned by the backend service before a timeout error is raised. Policy expressions are allowed. | No | N/A |
38
-
| http-version | The HTTP spec version to use when sending the HTTP response to the backend service. When using `2or1`, the gateway will favor HTTP /2 over /1, but fall back to HTTP/1 if HTTP/2 doesn't work. | No | 1 |
38
+
| http-version | The HTTP protocol version to use when sending the HTTP request to the backend service: <br> - `1`: HTTP/1 <br> - `2`: HTTP/2 <br/> - `2or1`: The gateway favors HTTP/2 over HTTP/1, but falls back to HTTP/1 if HTTP/2 doesn't work.<br/><br/> HTTP/2 outbound is supported in select gateways. See [Usage notes](#usage-notes) for details. | No | 1 |
39
39
| follow-redirects | Specifies whether redirects from the backend service are followed by the gateway or returned to the caller. Policy expressions are allowed. | No |`false`|
40
40
| buffer-request-body | When set to `true`, request is buffered and will be reused on [retry](retry-policy.md). | No |`false`|
41
41
| buffer-response | Affects processing of chunked responses. When set to `false`, each chunk received from the backend is immediately returned to the caller. When set to `true`, chunks are buffered (8 KB, unless end of stream is detected) and only then returned to the caller.<br/><br/>Set to `false` with backends such as those implementing [server-sent events (SSE)](how-to-server-sent-events.md) that require content to be returned or streamed immediately to the caller. Policy expressions aren't allowed. | No |`true`|
@@ -48,11 +48,18 @@ The `forward-request` policy forwards the incoming request to the backend servic
* Use the `http-version` attribute to enable the HTTP/2 protocol outbound from the gateway to the backend. Set the attribute to `2or1` or `2`. Currently, HTTP/2 outbound is supported in the self-hosted gateway and in preview in the v2 gateway.
54
+
55
+
> [!IMPORTANT]
56
+
> In the v2 gateway, HTTP/2 is supported inbound to the API Management gateway and outbound from the gateway to the backend but not end-to-end. Currently, the v2 gateway downgrades an incoming HTTP/2 connection to HTTP/1 before forwarding the request to the backend.
57
+
51
58
## Examples
52
59
53
60
### Send request to HTTP/2 backend
54
61
55
-
The following API level policy forwards all API requests to an HTTP/2 backend service.
62
+
The following API level policy forwards all API requests to an HTTP/2 backend service. For example, use this policy to forward requests from a self-hosted gateway to a gRPC backend.
56
63
57
64
```xml
58
65
<!-- api level -->
@@ -69,8 +76,6 @@ The following API level policy forwards all API requests to an HTTP/2 backend se
69
76
</policies>
70
77
```
71
78
72
-
This is required for HTTP /2 or gRPC workloads and currently only supported in self-hosted gateway. Learn more in our [API gateway overview](api-management-gateways-overview.md).
73
-
74
79
### Forward request with timeout interval
75
80
76
81
The following API level policy forwards all API requests to the backend service with a timeout interval of 60 seconds.
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments