Skip to content

Commit 40cdb44

Browse files
Merge pull request #271513 from ecfan/patch-2
Azure Logic Apps: HTTP action - Error thrown if "Content-Type" header is set to "application/json" but response doesn't actually contain JSON formatted content
2 parents c5e0ed0 + a7eecac commit 40cdb44

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

articles/connectors/connectors-native-http.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: logic-apps
55
ms.suite: integration
66
ms.reviewer: estfan, azla
77
ms.topic: how-to
8-
ms.date: 01/22/2024
8+
ms.date: 04/08/2024
99
---
1010

1111
# Call external HTTP or HTTPS endpoints from workflows in Azure Logic Apps
@@ -438,6 +438,12 @@ If an HTTP trigger or action includes these headers, Azure Logic Apps removes th
438438

439439
Although Azure Logic Apps won't stop you from saving logic apps that use an HTTP trigger or action with these headers, Azure Logic Apps ignores these headers.
440440

441+
<a name="mismatch-content-type"></a>
442+
443+
### Response content doesn't match the expected content type
444+
445+
The HTTP action throws a **BadRequest** error if the HTTP action calls the backend API with the `Content-Type` header set to **application/json**, but the response from the backend doesn't actually contain content in JSON format, which fails internal JSON format validation.
446+
441447
## Next steps
442448

443449
* [Managed connectors for Azure Logic Apps](/connectors/connector-reference/connector-reference-logicapps-connectors)

0 commit comments

Comments
 (0)