Discovery URLs are not HTTPs

1

I got the same issue as below described when the squidex behind a proxy server.
I tried to change enforceHttps to true. but it doesn’t work, it just keeps redirecting

TIM%E6%88%AA%E5%9B%BE20190507192220
TIM截图20190507192220.png1081×741 57.1 KB

image
image.png1572×444 28.5 KB

2

What is your baseUrl setting?

3

Your proxy server must set X-FORWARDED-PROTO header

4

Thanks!!!


:+1:

1 Like
5

HI Seamys. We have excatly th same problem. We have set X-FORWARDED-PROTO in the config for th site on the server with:

X-Forwarded-Proto

RequestHeader set "X-Forwarded-Proto" expr=%{REQUEST_SCHEME}

What did you use?

Thanks

Tiaan

6

I was thinking about using static values for hostname and protocol from the base url and just ignore all these headers.

This would make it much easier. But I am not sure if I miss any security issues. Right now I just follow best practices.