We moved our opendap server behind a load balancer which handles the
SSL handshake for https for us, then send the requests to our actual apache/tomcat
Server where opendap hyrax and bes live.
Now when we browse through our catalog and get to a data file, the ‘Data URL’
And the reformatting ‘buttons’ on the top, refer the user to https:<hostname>:80
Instead of https:<hostname>
You can see this by visiting:
And then choosing an HDF file to use OpenDAP services.
You’ll see the ‘Data URL’ that is displayed now contains :80 and the buttons
On the top fail when clicked and the url in the browser contains the un-good :80.
Our LB listens for https traffic on port 443, and forwards decrypted traffic on
Port 10443 to our apache/tomcat/hyrax server (bes lives on here too).
I’ve spoken with Nathan Potter a bit about this already, so he might be able
To fill in some blanks too.
Feel free to email me at this email address, call me at 303 709 7119, or Slack
Me on EOSDIS slack, handle schwabm.