Skip to content

Commit 670ec5a

Browse files
Merge pull request #247288 from dlepow/corspo
[APIM] CORS proxy in test console
2 parents 64e27a7 + 8d38558 commit 670ec5a

File tree

6 files changed

+7
-9
lines changed

6 files changed

+7
-9
lines changed

articles/api-management/api-management-howto-api-inspector.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ In this tutorial, you learn how to:
2222
> * Trace an example call
2323
> * Review request processing steps
2424
25-
:::image type="content" source="media/api-management-howto-api-inspector/api-inspector-002.png" alt-text="API inspector":::
25+
:::image type="content" source="media/api-management-howto-api-inspector/api-inspector-002.png" alt-text="Screenshot showing the API inspector." lightbox="media/api-management-howto-api-inspector/api-inspector-002.png":::
2626

2727
## Prerequisites
2828

@@ -36,7 +36,7 @@ To trace request processing, you must enable the **Allow tracing** setting for t
3636

3737
1. Navigate to your API Management instance and select **Subscriptions** to review the settings.
3838

39-
:::image type="content" source="media/api-management-howto-api-inspector/allow-tracing-1.png" alt-text="Allow tracing for subscription":::
39+
:::image type="content" source="media/api-management-howto-api-inspector/allow-tracing-1.png" alt-text="Screenshot showing how to allow tracing for subscription." lightbox="media/api-management-howto-api-inspector/allow-tracing-1.png":::
4040
1. If tracing isn't enabled for the subscription you're using, select the subscription and enable **Allow tracing**.
4141

4242
[!INCLUDE [api-management-tracing-alert](../../includes/api-management-tracing-alert.md)]
@@ -57,7 +57,7 @@ To trace request processing, you must enable the **Allow tracing** setting for t
5757
* If your subscription doesn't already allow tracing, you're prompted to enable it if you want to trace the call.
5858
* You can also choose to send the request without tracing.
5959

60-
:::image type="content" source="media/api-management-howto-api-inspector/06-debug-your-apis-01-trace-call-1.png" alt-text="Screenshot showing configure API tracing.":::
60+
:::image type="content" source="media/api-management-howto-api-inspector/06-debug-your-apis-01-trace-call-1.png" alt-text="Screenshot showing configure API tracing." lightbox="media/api-management-howto-api-inspector/06-debug-your-apis-01-trace-call-1.png":::
6161

6262
## Review trace information
6363

684 Bytes
Loading
26.7 KB
Loading
24.3 KB
Loading
24.3 KB
Loading
Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,16 @@
11
## Test the new API in the portal
2-
32
Operations can be called directly from the portal, which provides a convenient way for administrators to view and test the operations of an API.
4-
53
1. Select the API you created in the previous step.
64
1. Select the **Test** tab.
75
1. Select an operation.
8-
96
The page displays fields for query parameters and fields for the headers.
10-
117
> [!NOTE]
128
> In the test console, API Management automatically populates an **Ocp-Apim-Subscription-Key** header, and configures the subscription key of the built-in [all-access subscription](../articles/api-management/api-management-subscriptions.md#all-access-subscription). This key enables access to every API in the API Management instance. Optionally display the **Ocp-Apim-Subscription-Key** header by selecting the "eye" icon next to the **HTTP Request**.
13-
149
1. Depending on the operation, enter query parameter values, header values, or a request body. Select **Send**.
1510

16-
When the test is successful, the backend responds with **200 OK** and some data.
11+
When the test is successful, the backend responds with a successful HTTP response code and some data.
12+
13+
> [!TIP]
14+
> By default, the test console sends a request to API Management's CORS proxy, which forwards the request to the API Management instance, which then forwards it to the backend. This proxy uses public IP address 13.91.254.72 and can only reach public endpoints. If you want to send a request directly from the browser to the API Management service, select **Bypass CORS proxy**. Use this option when you want to use the test console and your API Management gateway is network-isolated or doesn't allow traffic from the CORS proxy.
1715
1816
To debug an API, see [Tutorial: Debug your APIs using request tracing](../articles/api-management/api-management-howto-api-inspector.md).

0 commit comments

Comments
 (0)