Comment by julik
2 days ago
The other option is not being overly strict with the data you receive from a client, especially when dealing with a protocol which is not a standard.
2 days ago
The other option is not being overly strict with the data you receive from a client, especially when dealing with a protocol which is not a standard.
I think the issue is that the client (the SDK) is complaining about a missing header it’s expecting to receive due to a new default in the client.
My guess is the client has options you pass in, they added a new default (or changed one, I’m not clear on that), and the new default sends something up to the server (header/param/etc) asking for the server to send back the new checksum header, the server doesn’t respond with the header, the client errors out.
Maybe I need to read more on this regression, you might be right.