Steps to reproduce:
The same as in MH-11786:
1. Run Opencast without HTTPS
2. Configure a HTTP proxy to use HTTPS and set the "X-Forwarded-SSL" header to "on". Configure Opencast to uses the proxy URL.
3. Configure LTI and try to run int
LTI redirect to the LTI tool via HTTP
LTI redirect to the LTI tool via HTTPS
The problem is caused by the `sendRedirect` method. Even after is fixed, it still thinks the request is served via HTTP. I could fix this by changing the passed location argument from a path to a whole URL (using the Opencast server URL). Since `sendRedirect` is used in other places, I'm not sure if this is the best way to solve this issue.
Should I give it a try to confirm if it works? Could you provide PR/commit?
, thanks yes - that would be helpful. Please add a comment to the PR with your testing results:
Work perfectly now.
Thanks a lot!
The short summary of this is that in Opencast 3.x, specifying a URL in tool=some.path parameter will cause Opencast to issue a redirect to http://some.domain/some.path.
In configurations where apache or nginx are the front-end proxy and forward https to Opencast on http, these redirects can be rewritten to https by using the ProxyPassReverse directive and equivalent configuration in nginx.
I'll leave this issue open until we've added example configurations to the docs.