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
Copy file name to clipboardExpand all lines: articles/api-management/transform-api.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ ms.author: danlep
16
16
17
17
In this tutorial, you learn about configuring [policies](api-management-howto-policies.md) to protect or transform your API. Policies are a collection of statements that are run sequentially on the request or response of an API that modify the API's behavior.
18
18
19
-
For example, you might want to set a custom response header. Or, protect your backend API by configuring a rate limit policy, so that the API isn't overused by developers. These examples are just an introduction to to API Management policies. For more policy options, see [API Management policies](api-management-policies.md).
19
+
For example, you might want to set a custom response header. Or, protect your backend API by configuring a rate limit policy, so that the API isn't overused by developers. These examples are a simple introduction to API Management policies. For more policy options, see [API Management policies](api-management-policies.md).
20
20
21
21
> [!NOTE]
22
22
> By default, API Management configures a global [`forward-request`](forward-request-policy.md) policy. The `forward-request` policy is needed for the gateway to complete a request to a backend service.
@@ -81,7 +81,7 @@ This section shows you how to configure a custom response header using the `set-
81
81
82
82
## Protect an API by adding rate limit policy (throttling)
83
83
84
-
This section shows how to add protection to your backend API by configuring rate limits, so that the API isn't overused by developers. This example shows how to configure the `rate-limit-by-key` policy using the code editor. In this example, the limit is set to three calls per 15 seconds. After 15 seconds, a developer can retry calling tge API.
84
+
This section shows how to add protection to your backend API by configuring rate limits, so that the API isn't overused by developers. This example shows how to configure the `rate-limit-by-key` policy using the code editor. In this example, the limit is set to three calls per 15 seconds. After 15 seconds, a developer can retry calling the API.
85
85
86
86
> [!NOTE]
87
87
> This policy isn't supported in the Consumption tier.
@@ -135,7 +135,7 @@ The rest of this section tests policy transformations that you set in this artic
135
135
### Test the custom response header
136
136
137
137
1. Select **Swagger Petstore** > **Test**.
138
-
1.SSelect the **GET Finds pets by status** operation, and optionally select a different value of the *status***Query parameter**. Select **Send**.
138
+
1.Select the **GET Finds pets by status** operation, and optionally select a different value of the *status***Query parameter**. Select **Send**.
139
139
140
140
As you can see, the custom response header is added:
0 commit comments