Thanks for responding. I may have chosen my words poorly. My issue is not that users are trying to go to a HTTPS page _initially_, then get the SSL error. I've read a lot of posts on that, and understand why HTTPS has issues being redirected.
My situation is different. I use HTTPS requests to do user authentication and I need those requests not to be redirected.
My login page loads as HTTP, displays buttons to login with Facebook, Twitter, etc.., when clicked those buttons initiate oauth requests to the given service. At this point, when the login window for Facebook should appear, I instead get the SSL error. I tried white listing all of the FB url's that appeared in Chrome's network debugger, but the issue persists. I may have missed some. Still trying to figure that out.
I tried making https://www.google.com
the login redirect page, and white listed "www.google.com
". And was able to get it to load. But I'm not able to replicate with Facebook.
Reflecting on this, it seems like I'm probably not white listing all the domains involved in FB auth.