You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My Nuxt 3 Implementation of this is a reverse proxy through an NGINX environment that goes from 443 https on the client to 80 on the docker container holding my nuxt 3 files/server.
sw.js changes my hostname from https://someplace.com to http://someplace.com and causes a mixed content error in the browser. Am I missing something? I've looked long and hard for a configuration solution to fix this. Please let me know if this is an oversight or an error on my part. Thanks.
The text was updated successfully, but these errors were encountered:
It seems it isn't even reading the correct url (strips the .com)
This is the console warning:
Mixed Content: The page at 'https://someplace.com/sw.js' was loaded over HTTPS, but requested an insecure resource 'http://someplace/'. This request has been blocked; the content must be served over HTTPS.
My Nuxt 3 Implementation of this is a reverse proxy through an NGINX environment that goes from 443 https on the client to 80 on the docker container holding my nuxt 3 files/server.
sw.js changes my hostname from https://someplace.com to http://someplace.com and causes a mixed content error in the browser. Am I missing something? I've looked long and hard for a configuration solution to fix this. Please let me know if this is an oversight or an error on my part. Thanks.
The text was updated successfully, but these errors were encountered: