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
wrote:
> On 16/10/2024 12
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
On 15/10/2024 5:11 μ.μ., Kevin Weis via nginx wrote:
have you tried to remove the trailing slash from the upstream url?
Hi Kevin,
Thanks for the hint.
I tried that but no, removing the trailing slash did not change anything.
Any other hints will be welcome!
Thanks again,
Nick
smime.p7s
Hi Nick,
have you tried to remove the trailing slash from the upstream url?
Turning: "proxy_pass http://example.private.noa.gr:80/;";
info: "proxy_pass http://example.private.noa.gr:80;";
If this resloves your issue, you can find the details in the docs here:
https://nginx.org/en/docs/http/ngx
Hello,
We are using nginx on a server as a reverse proxy and it works fine
serving multiple websites.
Now I am trying to reverse proxy another one, a WP website, in the same
way, but it won't render correctly.
I can only see the main page areas and only some text at some places,
but most c
