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/connectors/connectors-native-reqres.md
+19-6Lines changed: 19 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,6 +44,23 @@ With [Azure Logic Apps](../logic-apps/logic-apps-overview.md) and the built-in R
44
44
45
45
This built-in trigger creates a manually callable HTTPS endpoint that can receive *only* incoming HTTPS requests. When this event happens, the trigger fires and runs the logic app. For more information about the trigger's underlying JSON definition and how to call this trigger, see the [Request trigger type](../logic-apps/logic-apps-workflow-actions-triggers.md#request-trigger) and [Call, trigger, or nest workflows with HTTP endpoints in Azure Logic Apps](../logic-apps/logic-apps-http-endpoint.md).
46
46
47
+
> [!IMPORTANT]
48
+
> When you use the Request trigger, Logic Apps removes these headers when included, but without warning or error:
49
+
>
50
+
> *`Accept-*`
51
+
> *`Allow`
52
+
> *`Content-*` with these exceptions: `Content-Disposition`, `Content-Encoding`, and `Content-Type`
53
+
> *`Cookie`
54
+
> *`Expires`
55
+
> *`Host`
56
+
> *`Last-Modified`
57
+
> *`Origin`
58
+
> *`Set-Cookie`
59
+
> *`Transfer-Encoding`
60
+
>
61
+
> Although Logic Apps won't stop you from saving logic apps that use a
62
+
> Response action with these headers, Logic Apps ignores these headers.
63
+
47
64
1. Sign in to the [Azure portal](https://portal.azure.com). Create a blank logic app.
48
65
49
66
1. After Logic App Designer opens, in the search box, enter "http request" as your filter. From the triggers list, select the **When an HTTP request is received** trigger, which is the first step in your logic app workflow.
@@ -200,17 +217,13 @@ You can use the Response action to respond with a payload (data) to an incoming
200
217
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.
201
218
202
219
> [!IMPORTANT]
203
-
> If the Response action doesn't have a response body, Logic Apps removes
204
-
> these headers when included, but without warning or error:
220
+
> For any Response message, Logic Apps removes these headers when included, but without warning or error:
205
221
>
206
-
> * `Accept-*`
207
222
> * `Allow`
208
-
> * `Content-*` with these exceptions: `Content-Type`, `Content-Encoding`, and `Content-Disposition`
223
+
> * `Content-*` with these exceptions: `Content-Disposition`, `Content-Encoding`, and `Content-Type`
0 commit comments