This is not HTTP Chunked Transfer Encoding, this is a problem with the device expecting the entire request to appear in the first packet received.? This is never a safe assumption with TCP connections - you should expect anything from a MTU-sized packet to one byte per packet.? Unfortunately, not all devices are programmed correctly.? Jay are you using Crestron's HTTPClient to send the request?? Have you tried using a string in SIMPL+ to blast it all out in one chunk?? As long as it's smaller than the MTU I would expect it to go out in a single packet (though that's never guaranteed).
Thanks Alex.
I'm probably in the same boat.? But in my case, it is the
Crestron system that is sending messages chunked and causing the
issue.? I'm just hoping there is a setting, or possibly a way in
C#, to force the Crestron system not to do this.
Thanks again
Jay
On 9/21/2023 8:44 AM, Alex Teague
wrote:
I ran into this with a display driver I was creating a couple
years ago. I was never able to make things work properly.
Essentially the device I was working with would send all responses
chunked. I worked with several folks in ATSG on this and the end
result was that it was an issue with the device and no effective
way to work around receiving chunked data. I ran it up the chain
with the display manufacturer and they ended up changing things on
their end to fix it.
