You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While investigating overall HTTPS usage as part of #34, I discovered that during the API Umbrella v0.7 upgrade we rolled out in February (#180), our analytics stopped properly logging whether a request was made via HTTP or HTTPS. Instead, everything since February 9 has unfortunately been logging as HTTP, even if the request was actually made via HTTPS.
How we collect this information for analytics logging changed quite a bit in that v0.7 release, and it looks like this specific bit bit information was no longer being collected properly. Unfortunately, we can't really fix the past couple months worth of logging, but it would be good to fix this going forward. And for historical purposes, we at least have this information prior to February 7, so we we still have a pretty good idea of overall HTTP vs HTTPS traffic trends.
The text was updated successfully, but these errors were encountered:
Fixed by NREL/api-umbrella-router@b989713 and tests added to our integration suite around this logging behavior to help ensure this doesn't break again.
While investigating overall HTTPS usage as part of #34, I discovered that during the API Umbrella v0.7 upgrade we rolled out in February (#180), our analytics stopped properly logging whether a request was made via HTTP or HTTPS. Instead, everything since February 9 has unfortunately been logging as HTTP, even if the request was actually made via HTTPS.
How we collect this information for analytics logging changed quite a bit in that v0.7 release, and it looks like this specific bit bit information was no longer being collected properly. Unfortunately, we can't really fix the past couple months worth of logging, but it would be good to fix this going forward. And for historical purposes, we at least have this information prior to February 7, so we we still have a pretty good idea of overall HTTP vs HTTPS traffic trends.
The text was updated successfully, but these errors were encountered: