Figured it out. Look for "HTTP_X_FORWARDED_PROTO" in the request header. The value will either be "http" or "https"
On Jan 11, 2:37 pm, Joe K <[email protected]> wrote: > I figured out at least part of my problem...the SSL Redirect > middleware. > > More specifically, request.is_secure() is ALWAYS returning false, even > when on a secure URL. > > I suspect that Heroku sets a different header than Django is expecting > (or no header at all) to note a request as secure. > > Any ideas? Either the headers that Heroku does help, or another way of > detecting whether or not the request is secure would be great. > > (I suspect looking for https is not good enough...) > > Thanks > > Joe > > On Jan 11, 12:26 pm, Joe K <[email protected]> wrote: > > > > > > > > > I am trying to deploy a Satchmo-based Django app on Heroku, and > > everything works beautifully on the bulk of the site...until I go to > > check out and get redirected to https. > > > I installed the piggyback SSL plugin, so that's not the problem, but > > as soon as I try to go to anyhttps://myapp.herokuapp.comaddressI > > get stuck in a redirect loop. > > > Is there a modification I need to make to my WSGI file, or settings > > file, to get a Django app to work with SSL on Heroku? > > > Thanks in advance. > > > Joe K -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
