Drive authentication window timeout not obvious

During a customized authentication, the drive login window (after username and password is entered) is receiving a redirect that is invalid (tested case is an HTTP URL whereas the server is only running on HTTPS).
If that URL never responds, Drive keeps trying, but there is no indication of what is happening (why it never succeeds) in the logs. The process does not fail gracefully or with any message to indicate what happened – it seems to get stuck in a loop.

Consider adding some logging to show a connection is being attempted that never succeeds.