1 x (application) LoadBalancer, 2 listeners, each with 1 certificate/domain, 2 x custom ORDS (standalone) → 2 APEX on ADB
( SSL is being terminated at the load balancer. ORDS to APEX is over 8080 )
Config1 is ORDS 24.2 / latest APEX
Config2 is ORDS 25.1 / latest APEX
In Config2 I encounter 502 Bad Gateway which I worked around by following
set security.httpsHeaderCheck "X-Forwarded-Proto: https"
as mention here https://peterobrien.blog/2023/02/12/https-load-balance-nginx-ords/ ( even though I have no proxy )
This setting appears to be new in 25.1 ( not mentioned in 24.2 docs )
https://docs.oracle.com/en/database/oracle/oracle-rest-data-services/25.1/ordig/about-REST-configuration-files.html
Specifies the HTTP request header and value that indicates to ORDS the initial client request was received by a Load Balancer / Reverse Proxy over HTTPS even if the request received by ORDS was sent over HTTP.
Qu: is this the best / only way to avoid 502 ?
( I am hoping for an official response from Oracle but happy with any advice from community )
I suspect security.forceHTTPS might also work - but I cound not find it documentation.
Other useful references
https://blogs.oracle.com/coretec/post/running-oracle-rest-data-services-ords-on-kubernetes
https://forums.oracle.com/ords/apexds/post/apex-authentication-get-callback-url-returning-http-url-ins-0066
https://blog.cloudnueva.com/running-ords-standalone-mode
https://promatis.com/de/en/lessons-learned-while-upgrading-apex-and-ords-to-22-1/