You could consider adding a CSP header to cause clients to automatically
fetch those resources over HTTPS:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/upgrade-insecure-requests
On Wed, 16 Oct 2024 at 00:06, Nikolaos Milas via nginx <nginx@nginx.org>
wrote:
> On 16/10/2024 12:19 π.μ., Nikolaos Milas via nginx wrote:
>
> > ...
> > I tried that but no, removing the trailing slash did not change anything.
> > ...
>
> I found that the problem is that, as the proxied page is rendered over
> SSL, browsers are auto-blocking parts of the page as non-secure.
>
> This is due, I guess, to the fact that multiple page items are probably
> hardcoded as http rather than as https links or as absolute rather than
> as relative paths (images etc).
>
> I'll have to ask the developer to check the app throughout.
>
> Sorry for the fuss.
>
> All the best,
> Nick
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> https://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
https://mailman.nginx.org/mailman/listinfo/nginx