fix: Build HTTPS redirect URI when behind LB

[iskandar]

Issue/Feature

When running s3-proxy behind a TLS-terminating Load Balancer, s3-proxy generates a http:// value for
the OIDC redirect_uri. In HTTPS-only environments (or with secure cookies enabled), this causes the OIDC flow to fail.

This PR adds a simple check for the de-facto standard HTTP Header X-Forwarded-Proto. If this header is set and has value https, the GetRequestURI function will use the https scheme instead of http.

Checklist:

• Verified by team member
• Tests were added
• Comments where necessary
• Documentation changes if necessary

[iskandar]

I guess the 'labeling' GitHub Actions fail because this remote fork doesn't have access to the GitHub Token.

[iskandar]

Tests actually pass in CircleCI, but the process fails trying to run Coveralls - again, probably because the fork doesn't have permission to use the token.

[oxyno-zeta]

Hello @iskandar !

Yes it is because of all of this. Forks cannot have access to my tokens. I will try to work on a patch to avoid running those steps when comes from a PR.

By the way, the PR will be merged as everything important to me (linter, tests are green, builds are ok) are working.

Thanks for your contribution !

[oxyno-zeta]

Merged, will be packaged in the next release 👍

[iskandar]

Thanks, and thanks for building a useful project :)

[oxyno-zeta]

Happy to see that this project is used and help some people ! 😉

[oxyno-zeta]

🎉 This PR is included in version 3.3.0 🎉

The release is available on:

• GitHub release
• v3.3.0

Your semantic-release bot 📦🚀