I was using the system last night, and was using a dashboard that has an option to send me back a “slice” of textual data as an InfoMessage, and it kept failing.
It used to work properly as coded, which was to send back 4096 bytes, or less.
Now it seems to have the following behavior:
1754 characters - Message comes back successfully → Success
1755 characters - Message comes back → successfully but then …
ErrorAfter: Unable to read beyond the end of the stream.
1756 characters - Error:Unknown REST exception:
<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.23.2</center>
</body>
</html>
I wonder if the message is being passed through the http header, which is limited. The 1.7K plus other cookies, etc. might have pushed it over a limit.
It is, and that has lowered the practical limit to significantly lower that when they were using WCF, however, it has been up until recently still been supporting at least up to 10k characters, which is as far as I bothered to test before.
I decided to change environments, and I believe it’s isolated to my AKS CAAB instance.
They must have lower limits set, for what reason, I don’t know why. I will have to ask.
I moved into my Pilot environment, which is also 2023.1.8 and just sent 40k bytes back.
