Looking for suggestions on how to configure both http://www.domain and http://domain to https://www.domain. I believe it should not be too difficult with advanced load balancer but the options are overwhelming. We are using a bucket in the backend.
For now our dns records points to the external lb address and the certificates covers both names. Everything works except we have problems with CORS policies on the themify theme failing on https://domain. Rewriting the headers is probably also possible with advanced load balancer but looks more complex at first sight.
Hello Brunoimpens
Cross-origin resource sharing policies are applicable only for Internal HTTP(S) load balancers. [1] I am not able to see from what error we are getting when trying to Open any link you provided,for internal TCP load balancer wherein this security feature isn't available as per [1]. I suggest configuring an Internal HTTP(S) LB to set up CORS policies for this use case. This document [2] can be referred for traffic management to configure CORS policies to handle internal HTTP(S) Load Balancing settings for enforcing CORS requests. I hope this helps. Thank you.
[1] https://cloud.google.com/load-balancing/docs/features#security