Dear Wagner,
I have recently migrated several of my XData servers from a basic cloud setup to a new online infrastructure. In this new environment, all incoming traffic is routed through a central reverse proxy using HTTPS. This proxy forwards the requests to the appropriate backend servers, which all run over HTTP only, since the internal network is completely isolated from the outside world.
The XData servers themselves seem to be running correctly so far (I haven’t completed full testing yet), but the Swagger UI is not working. I'm receiving browser errors related to mixed content (HTTPS/HTTP) when trying to access the Swagger documentation. Please see the attached screenshots for reference.
My questions are:
Where should I apply a fix for this issue?
In the reverse proxy configuration? (I’ve already tried several adjustments, but none have resolved the issue.)
In the XData server configuration?
Is this kind of architecture (HTTPS proxy in front of HTTP-only XData servers) generally supported when using Swagger UI?
Any guidance or recommended setup for such deployments would be greatly appreciated.
Best regards,
Thomas
P.S.:
I came across this post which seems related to my issue. However, I would prefer to try solving it by properly configuring the nginx reverse proxy.
Is that possible? If not, is there a more detailed guide available for the solution described in the post?
