One of the underlying issues leading to #40 being filed is that we do not specify the appropriate content-type as part of our requests to BMO. While they're restoring the surprise default that we uncovered, we should still make every effort — regardless of #40 or not — to ensure that we're setting the appropriate Content-Type header on our requests.
One of the underlying issues leading to #40 being filed is that we do not specify the appropriate content-type as part of our requests to BMO. While they're restoring the surprise default that we uncovered, we should still make every effort — regardless of #40 or not — to ensure that we're setting the appropriate Content-Type header on our requests.
For our current BMO code, we should use:
And for future issue #40 BMO code, we should use:
Fixing this issue would restore service for B-K tonight, or else it'll be restored tomorrow by a server-side repair.