This update adds the capability to fetch history events on the server side. If you haven't declared custom events for a specific date, the default fallback is to fetch an event for the date from an external server, traditionally this was done on the client side but due to the external resource not supporting https some browsers prevented the fetch from happening, this fixes the issue by moving the fetch to happen on the server when the response is being prepared.
This approach has some performance implications since a synchronous http call is made within the request response cycle.This could mean that if the external resource takes long to respond it could delay response to the user.In case of failure it fails gracefully.Custom defined history events are not affected by this overhead.
