When we have paginated list endpoints, the "next" page URL is mistakenly HTTP. We suspect this is because the URL is constructed based on the current request scheme. edx-platform seems to workaround this issue by setting SECURE_PROXY_SSL_HEADER which overrides the current request scheme when DRF tries to fetch it to construct a next URL, so this PR is mimicking that behavior.
Enterprise also does the same, and that is where we mostly copy-pasted this PR from.
PROD 4118
When we have paginated list endpoints, the "next" page URL is mistakenly HTTP. We suspect this is because the URL is constructed based on the current request scheme. edx-platform seems to workaround this issue by setting SECURE_PROXY_SSL_HEADER which overrides the current request scheme when DRF tries to fetch it to construct a next URL, so this PR is mimicking that behavior.
Enterprise also does the same, and that is where we mostly copy-pasted this PR from.
Internal Slack discussions for more context
https://twou.slack.com/archives/C04ACDVM6A1/p1720630664588599
https://twou.slack.com/archives/C049BVC75J7/p1720627508164049