Solve the problem with mixed http and https content

[bajiat]

After removing Force-SSL package due to dockerization, we are experiencing problems in deployment e.g. with Github authentication in nightly (see #1095), and in viewing Swagger files if in http (see #1101)

Propose the most optimal solution for this without causing too much pain on deployment configuration. May require changing dockerization.

[bajiat]

@shaliko Any comments / suggestions on this?

[shaliko]

@bajiat @brylie At lease first issue #1095 happen because nightly.apinf.io available by HTTPS and HTTP. Before I removed "Force-SSL" there was redirect from HTTP to HTTPS.

I think the right way for fix issue is update Nginx conf (mupx), handling SSL not app a responsibility. I am checking how update mupx settings.

[brylie]

Alright, we will need to ensure our mupx and Docker deployments are HTTPS only.

[bajiat]

@shaliko The suggestion from Tampere team is to add Force-SSL back to the project, because removing it is causing multiple problems. What would the options for / changes needed to Docker? Is "one-command" installation still possible?

[shaliko]

@brylie I can don't know all details, but are we really need be HTTPS only? If application be agnostic to HTTP/HTTPS? The issue was because callback URL from github was configured only for HTTPS.