An Origin user reported this issue: http://stackoverflow.com/questions/20862510/how-to-determine-if-an-incoming-url-request-to-an-openshift-python-3-3-app-is-h/20864649#20864649 It's possible that a) the library they were using no longer supports direct [] access on the "request" object b) We stopped sending HTTP_X_FORWARDED_PROTO the same way c) A change to mod_wsgi changed how these things were set, and that change is 1) intentional 2) intentional Not sure what the cause is - I suspect C), but we need to be sure it was intentional. If it was intentional, we can simply respond to the stack overflow question.
Using the Python 3 WSGI application interface gives you access to the environment and a response object. The user didn't provide enough information about their http middleware to reproduce their issue. Their library apparently provides to them a request abstraction (and indirectly, access to environment, which according to them contains the header they want). Any regression would likely be in the library they're using. I verified that in a Python 3 app using the wsgi application interface that the HTTP_X_FORWARDED_PROTO value from environment is correct. Feel free to re-open the bug if there is concrete evidence of (or a means to reproduce) a platform regression.