Skip to content

Commit a288e60

Browse files
committed
Modified screenshots and content for US-1890458
1 parent 8185e3f commit a288e60

File tree

7 files changed

+9
-9
lines changed

7 files changed

+9
-9
lines changed
11.6 KB
Loading
-14.1 KB
Loading
-20.1 KB
Loading
-4.46 KB
Loading

articles/api-management/transform-api.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,9 @@ ms.author: danlep
1212

1313
# Tutorial: Transform and protect your API
1414

15-
In this tutorial, you'll learn how to transform your API so it doesn't reveal private backend info. Transforming an API might help you to hide the technology stack info that is running in the backend. You can also hide the original URLs that appear in the body of the API's HTTP response. And then, you could redirect them to an API Management gateway.
15+
In this tutorial, you'll learn how to transform your API so it doesn't reveal private backend info. Transforming an API might help you hide the technology stack info that's running in the backend. It also helps you hide the original URLs that appear in the body of the API's HTTP response. And then, redirect the URLs to an API Management gateway.
1616

17-
The tutorial also explains how to add protection to your backend API by configuring a rate limit with Azure API Management. You may want to limit the rate of API calls so the API isn't overused by developers. For more information, see [API Management policies](api-management-policies.md).
17+
The tutorial also explains how to add protection to your backend API by configuring a rate limit with Azure API Management. You might want to limit the rate of API calls so the API isn't overused by developers. For more information, see [API Management policies](api-management-policies.md).
1818

1919
In this tutorial, you learn how to:
2020

@@ -38,7 +38,7 @@ In this tutorial, you learn how to:
3838

3939
## Transform an API to strip response headers
4040

41-
This section shows how to hide the HTTP headers that you don't want to show to your users. The section also explains how to delete the following headers in the HTTP response:
41+
This section shows how to hide the HTTP headers that you don't want to show to your users. And this section explains how to delete the following headers in the HTTP response:
4242

4343
* **X-Powered-By**
4444
* **X-AspNet-Version**
@@ -118,7 +118,7 @@ To see the original response:
118118

119119
## Protect an API by adding rate limit policy (throttling)
120120

121-
This section shows how to add protection to your backend API by configuring rate limits. You may also want to limit the rate of API calls so that the API isn't overused by developers. In this example, the limit is set to three calls per 15 seconds for each subscription ID. After 15 seconds, a developer can retry calling an API.
121+
This section shows how to add protection to your backend API by configuring rate limits. You might also want to limit the rate of API calls so that the API isn't overused by developers. In this example, the limit is set to three calls per 15 seconds for each subscription ID. After 15 seconds, a developer can retry calling an API.
122122

123123
1. Select **Demo Conference API** > **Design** > **All operations**.
124124
1. In the **Inbound processing** section, select the code editor (**</>**) icon.
@@ -169,7 +169,7 @@ The rest of this section tests policy transformations that you set in this artic
169169
### Test the stripped response headers
170170
171171
1. Select **Demo Conference API** > **Test**.
172-
1. Select the **GetSpeakers** operation, and then select **Send**.
172+
1. Select the **GetSpeakers** operation and select **Send**.
173173
174174
As you can see, the headers have been stripped:
175175
@@ -178,9 +178,9 @@ The rest of this section tests policy transformations that you set in this artic
178178
### Test the replaced URL
179179
180180
1. Select **Demo Conference API** > **Test**.
181-
1. Select the **GetSpeakers** operation, and then select **Send**.
181+
1. Select the **GetSpeakers** operation and select **Send**.
182182
183-
As you can see, the URLs have been replaced.
183+
As you can see, the URLs are replaced.
184184
185185
:::image type="content" source="media/transform-api/test-replaced-url.png" alt-text="Replaced URLs":::
186186
@@ -193,7 +193,7 @@ The rest of this section tests policy transformations that you set in this artic
193193
194194
:::image type="content" source="media/transform-api/test-throttling-new.png" alt-text="Too many requests":::
195195
196-
1. Wait for 15 seconds or more, and then select **Send** again. This time you should get a **200 OK** response.
196+
1. Wait for 15 seconds or more and then select **Send** again. This time you should get a **200 OK** response.
197197
198198
## Next steps
199199

includes/api-management-navigate-to-instance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.author: vlvinogr
99

1010
1. In the Azure portal, search for and select **API Management services**.
1111

12-
:::image type="content" source="media/api-management-navigate-to-instance/view-apim-1.png" alt-text="Select API Management services":::
12+
:::image type="content" source="media/api-management-navigate-to-instance/view-apim-1-new.png" alt-text="Select API Management services":::
1313

1414
1. On the **API Management services** page, select your API Management instance.
1515

52.5 KB
Loading

0 commit comments

Comments
 (0)