Skip to content

Commit 9218337

Browse files
committed
Updating after moniker
1 parent cc9458d commit 9218337

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/iot-edge/iot-edge-limits-and-restrictions.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -105,13 +105,13 @@ Changes made in `config.toml` to `edgeAgent` environment variables like the `hos
105105

106106
When using Node.js to send device to cloud messages with the AMQP protocol to an IoT Edge runtime, messages stop sending after 2047 messages. No error is thrown and the messages eventually start sending again, then cycle repeats. If the client connects directly to Azure IoT Hub, there's no issue with sending messages. This issue has been fixed in IoT Edge 1.2 and later.
107107

108+
:::moniker-end
109+
<!-- end 1.1 -->
110+
108111
### NTLM Authentication
109112

110113
IoT Edge does not currently support network proxies that use NTLM authentication. Users may consider bypassing the proxy by adding the required endpoints to the firewall allow-list.
111114

112-
:::moniker-end
113-
<!-- end 1.1 -->
114-
115115
## Next steps
116116

117117
For more information, see [IoT Hub other limits](../iot-hub/iot-hub-devguide-quotas-throttling.md#other-limits).

0 commit comments

Comments
 (0)