Merge pull request #106575 from ecfan/http

Add notes that various headers are removed from HTTP calls and Response actions

Author: American-Dipper

articles/connectors/connectors-native-http.md

@@ -1,25 +1,47 @@
 ---
-title: Call HTTP and HTTPS endpoints
-description: Send outgoing requests to HTTP and HTTPS endpoints by using Azure Logic Apps
+title: Call service endpoints by using HTTP or HTTPS
+description: Send outbound HTTP or HTTPS requests to service endpoints from Azure Logic Apps
 services: logic-apps
 ms.suite: integration
 ms.reviewer: klam, logicappspm
 ms.topic: conceptual
-ms.date: 07/05/2019
+ms.date: 03/12/2020
 tags: connectors
 ---
 
-# Send outgoing calls to HTTP or HTTPS endpoints by using Azure Logic Apps
+# Call service endpoints over HTTP or HTTPS from Azure Logic Apps
 
-With [Azure Logic Apps](../logic-apps/logic-apps-overview.md) and the built-in HTTP trigger or action, you can create automated tasks and workflows that regularly send requests to any HTTP or HTTPS endpoint. To receive and respond to incoming HTTP or HTTPS calls instead, use the built-in [Request trigger or Response action](../connectors/connectors-native-reqres.md).
+With [Azure Logic Apps](../logic-apps/logic-apps-overview.md) and the built-in HTTP trigger or action, you can create automated tasks and workflows that send requests to service endpoints over HTTP or HTTPS. For example, you can monitor the service endpoint for your website by checking that endpoint on a specific schedule. When the specified event happens at that endpoint, such as your website going down, the event triggers your logic app's workflow and runs the actions in that workflow. If you want to receive and respond to inbound HTTPS calls instead, use the built-in [Request trigger or Response action](../connectors/connectors-native-reqres.md).
 
-For example, you can monitor the service endpoint for your website by checking that endpoint on a specified schedule. When a specific event happens at that endpoint, such as your website going down, the event triggers your logic app's workflow and runs the specified actions.
+> [!NOTE]
+> Based the target endpoint's capability, the HTTP connector supports Transport Layer Security (TLS) 
+> versions 1.0, 1.1, and 1.2. Logic Apps negotiates with the endpoint over using the highest supported 
+> version possible. So for example, if the endpoint supports 1.2, the connector uses 1.2 first. 
+> Otherwise, the connector uses the next highest supported version.
 
-To check or *poll* an endpoint on a regular schedule, you can use the HTTP trigger as the first step in your workflow. On each check, the trigger sends a call or *request* to the endpoint. The endpoint's response determines whether your logic app's workflow runs. The trigger passes along any content from the response to the actions in your logic app.
+To check or *poll* an endpoint on a recurring schedule, [add the HTTP trigger](#http-trigger) as the first step in your workflow. Each time that the trigger checks the endpoint, the trigger calls or sends a *request* to the endpoint. The endpoint's response determines whether your logic app's workflow runs. The trigger passes any content from the endpoint's response to the actions in your logic app.
 
-You can use the HTTP action as any other step in your workflow for calling the endpoint when you want. The endpoint's response determines how your workflow's remaining actions run.
+To call an endpoint from anywhere else in your workflow, [add the HTTP action](#http-action). The endpoint's response determines how your workflow's remaining actions run.
 
-Based the target endpoint's capability, the HTTP connector supports Transport Layer Security (TLS) versions 1.0, 1.1, and 1.2. Logic Apps negotiates with the endpoint over using the highest supported version possible. So, for example, if the endpoint supports 1.2, the connector uses 1.2 first. Otherwise, the connector uses the next highest supported version.
+> [!IMPORTANT]
+> If an HTTP trigger or action includes these headers, Logic Apps removes these 
+> headers from the generated request message without showing any warning or error:
+>
+> * `Accept-*`
+> * `Allow`
+> * `Content-*` with these exceptions: `Content-Disposition`, `Content-Encoding`, and `Content-Type`
+> * `Cookie`
+> * `Expires`
+> * `Host`
+> * `Last-Modified`
+> * `Origin`
+> * `Set-Cookie`
+> * `Transfer-Encoding`
+>
+> Although Logic Apps won't stop you from saving logic apps that use an 
+> HTTP trigger or action with these headers, Logic Apps ignores these headers.
+
+This article shows how to add an HTTP trigger or action to your logic app's workflow.
 
 ## Prerequisites
 
@@ -31,13 +53,15 @@ Based the target endpoint's capability, the HTTP connector supports Transport La
 
 * The logic app from where you want to call the target endpoint. To start with the HTTP trigger, [create a blank logic app](../logic-apps/quickstart-create-first-logic-app-workflow.md). To use the HTTP action, start your logic app with any trigger that you want. This example uses the HTTP trigger as the first step.
 
+<a name="http-trigger"></a>
+
 ## Add an HTTP trigger
 
 This built-in trigger makes an HTTP call to the specified URL for an endpoint and returns a response.
 
 1. Sign in to the [Azure portal](https://portal.azure.com). Open your blank logic app in Logic App Designer.
 
-1. Under **Choose an action**, in the search box, enter "http" as your filter. From the **Triggers** list, select the **HTTP** trigger.
+1. Under the designer's search box, select **Built-in**. In the search box, enter `http` as your filter. From the **Triggers** list, select the **HTTP** trigger.
 
    ![Select HTTP trigger](./media/connectors-native-http/select-http-trigger.png)
 
@@ -58,6 +82,8 @@ This built-in trigger makes an HTTP call to the specified URL for an endpoint an
 
 1. When you're done, remember to save your logic app. On the designer toolbar, select **Save**.
 
+<a name="http-action"></a>
+
 ## Add an HTTP action
 
 This built-in action makes an HTTP call to the specified URL for an endpoint and returns a response.
@@ -70,7 +96,7 @@ This built-in action makes an HTTP call to the specified URL for an endpoint and
 
    To add an action between steps, move your pointer over the arrow between steps. Select the plus sign (**+**) that appears, and then select **Add an action**.
 
-1. Under **Choose an action**, in the search box, enter "http" as your filter. From the **Actions** list, select the **HTTP** action.
+1. Under **Choose an action**, select **Built-in**. In the search box, enter `http` as your filter. From the **Actions** list, select the **HTTP** action.
 
    ![Select HTTP action](./media/connectors-native-http/select-http-action.png)
 

articles/connectors/connectors-native-reqres.md

@@ -1,15 +1,15 @@
 ---
-title: Receive and respond to HTTPS calls
-description: Handle HTTPS requests and events in real time by using Azure Logic Apps
+title: Receive and respond to calls by using HTTPS
+description: Handle inbound HTTPS requests from external services by using Azure Logic Apps
 services: logic-apps
 ms.suite: integration
 ms.reviewers: klam, logicappspm
 ms.topic: conceptual
-ms.date: 01/14/2020
+ms.date: 03/12/2020
 tags: connectors
 ---
 
-# Receive and respond to incoming HTTPS calls by using Azure Logic Apps
+# Receive and respond to inbound HTTPS requests in Azure Logic Apps
 
 With [Azure Logic Apps](../logic-apps/logic-apps-overview.md) and the built-in Request trigger or Response action, you can create automated tasks and workflows that receive and respond to incoming HTTPS requests. For example, you can have your logic app:
 
@@ -199,6 +199,21 @@ You can use the Response action to respond with a payload (data) to an incoming
 
 Your logic app keeps the incoming request open only for one minute. Assuming that your logic app workflow includes a Response action, if the logic app doesn't return a response after this time passes, your logic app returns a `504 GATEWAY TIMEOUT` to the caller. Otherwise, if your logic app doesn't include a Response action, your logic app immediately returns a `202 ACCEPTED` response to the caller.
 
+> [!IMPORTANT]
+> If a Response action includes these headers, Logic Apps removes these headers 
+> from the generated response message without showing any warning or error:
+>
+> * `Allow`
+> * `Content-*` with these exceptions: `Content-Disposition`, `Content-Encoding`, and `Content-Type`
+> * `Cookie`
+> * `Expires`
+> * `Last-Modified`
+> * `Set-Cookie`
+> * `Transfer-Encoding`
+>
+> Although Logic Apps won't stop you from saving logic apps that have a 
+> Response action with these headers, Logic Apps ignores these headers.
+
 1. In the Logic App Designer, under the step where you want to add a Response action, select **New step**.
 
    For example, using the Request trigger from earlier: