Hey John, thanks for the reply.
Unless I'm missing what you are saying, my problem isn't my own servers, they are all ssl enabled and fully certed, it's requesting layers from others (namely gis.fema.gov, see example). Using the proxy on my server for services on that server works great, it's the initial check for CORS that you mentioned that disregards the proxy and causes me the http over https warning that is giving me indigestion.
It seems my options are either go forward with warnings from the browser, convince fema to enable https traffic on their servers, or create a custom proxy on my servers.