TLS失败，ERROR_INVALID_RECORD（5007）仅在某些wifi上发生

我有一个旧版本的SDK，3.1.2，与目前在该领域的设备的问题。我有一个无法解释的问题，其中我从“WICEDEJTCPILISTRAYRIDE”返回5007，表示一个无效的TLS记录。
TCP+TLS流在一种机制中被读取，其中文件通过手动打开套接字、建立TLS上下文、创建流、构建HTTP请求、将其发送到流、解析HTTP头响应、然后在一个时间内抓取二进制体1024字节而被读取。直到最后。
特别奇怪的是，这个代码在WiFi AP的95%上运行良好，但是在移动热点WiFi（包括iPhone 6S）上，它将通过下载在同一点上命中这个错误。该文件是~300 KB，错误将发生在80K，可重复地，总是在相同的长度通过流。
我在一个平台上运行，这个平台有点资源受限，有128KB的RAM。然而，它再次在一些WiFi AP上运行良好，而不是在其他人上。
我已经用NGiNX服务器测试了它，它使用16KB TLS记录和2KB TLS记录，每一个都使用“SSLBuffReSythSigy”参数，这两种情况都存在问题。
我正在调试硬件上运行它，但是没有遇到调试或与MALLC相关的断点或硬件故障。
据我所知，失败是` wiced_tls_receive_packet `，750号线，在打电话：结果= tls_get_next_record（上下文，&；记录，超时，tls_receive_packet_if_needed）；
不幸的是，我不能走的更深，因为贝斯勒在3.1.2是二进制。
我不知道足够的关于TLS在想做调试的结果在` wiced_tls_receive_packet `。
关于为什么会发生这样的事情有什么想法吗？



以下为原文
I am having an issue with an old version of the SDK, 3.1.2, with devices that are presently in the field. I am having an unexplained issue wherein I get return 5007 from `wiced_tcp_stream_read`, indica ting an invalid TLS record.

The TCP+TLS stream is being read in a mechanism whereby a file is downloaded by manually opening a socket, setting up a TLS context, creating a stream, constructing an HTTP request, sending it to the stream, parsing the HTTP header response, and then grabbing the binary body 1024 bytes at a time until the end.

The particularly odd thing is that this code works fine on 95% of wifi AP's, but on a mobile hotspot wifi (including an iPhone 6S), it will hit this error at the same point through the download. The file is ~300KB, and the error will happen at ~80K, repeatably, always in the same length through stream.

I am running on a platform that is *somewhat* resource constrained, with 128KB of RAM. However, again: it works fine on some WiFi AP's, and not on others.

I have tested this with an nginx server that uses both 16KB TLS records and 2KB TLS records, per the `ssl_buffer_size` parameter, and the problem exists for both cases.
I am running it on hardware with a debug build, but no debug or malloc-related breakpoints or hardfaults are being hit.

As far as I can tell, the failure is in `wiced_tls_receive_packet`, line 750, on the call to :
result = tls_get_next_record( context, &record, timeout, TLS_RECEIVE_PACKET_IF_NEEDED );

Unfortunately, I can't go deeper than that, since BESL in 3.1.2 is a binary.
I don't quite know enough about TLS at the moment to try and do debugging around the results within `wiced_tls_receive_packet`.

Any ideas as to why this is happening?