We were notified by a customer a few days ago that they were experiencing some issues with our Geotab integration, and after some investigation, we determined that Rule Notification web requests started coming in with the "text/plain" Content-Type header, instead of "application/x-www-url-formencoded" as they usually do. This caused cascading failures for many of our customer integrations and required us to override the Content-Type header in API forwarding middleware wherever possible.

The only event we've noticed that seems to correlate to that change is a database update from 11333.561 to 11333.585. The update was completed ~90 seconds after our telemetry indicates that the first webhook failures started.

Is this an intentional change to the Content-Type header of notification web requests in a recent update, or should we be reporting this as a bug? I've tried to find release notes or other documentation specific to database version 11333.561 (or any database version, for that matter) but could only find info for general MyGeotab releases.