Mixed content error #1965
Comments
|
Yes, mixed content is impossible in modern browsers. No way around that. https://ogc-demo.k8s.ilt-dmz.iosb.fraunhofer.de/v1.1 All run on the same URL. |
|
I know it can be run on same url. But if i used this approach then there is an error from keycloak as i am using keycloak for auth.keycloak is removing /port from the redirect url and returning acess_token like url/?access_token=123. where as it should actually return url/port?access_token=123. So therefore i am trying to put my frost still on http |
|
That sounds like a mis-configured KeyCloak instance. Regardless, mixed content is not possible in modern browsers. There is no way around that. |
|
did you used keycloak to authorize these frost instances if you did. Did you faced similar issue ? |
|
Those are not secured, but in difference instances we've not had redirect issues that were not directly related to mis-configured redirect URLs in KeyCloak. |
I am facing mix content error. My react application is running on https. while my frost server is on http. when creating things i am facing this error Mixed Content: The page at 'https://sensorhub-dev.hef.tum.de/devices/store#iss=https%3A%2F%2Fkeycloak-dev.hef.tum.de%2Frealms%2Fmaster' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://tuzehez-dev.srv.mwn.de:6062/FROST-Server/v1.0/Things'. This request has been blocked; the content must be served over HTTPS. I cannot put my frost server on https because there will be multiple frost instances.
The text was updated successfully, but these errors were encountered: