That's exactly it. I followed the suggestion from a Stack Overflow post and added a check to see whether 'x-forwarded-proto' = 'https'.
http://stackoverflow.com/questions/7185074/heroku-nodejs-http-to-https-ssl-forced-redirect On Monday, November 21, 2011 8:26:46 AM UTC-7, j_McCaffrey wrote: > > Not sure what the official answer would be, but can you app detect the non > ssl connection and redirect or refuse? > > On Tue, Nov 15, 2011 at 11:51 PM, Benny Tsai <[email protected]> wrote: > >> Hi all, >> >> I have a web service (written using Clojure & Noir) that I want to make >> accessible over SSL. I've enabled the Piggyback SSL add-on (gratifyingly >> easy to use!), but noticed that my service is still accessible through the >> old plain HTTP URL. Is there a way to make the service *only* accessible >> over SSL? Many thanks in advance. >> >> -Benny >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Heroku" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/heroku/-/0gbI-yOJbZgJ. >> 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. >> > > > > -- > Thanks, > -John > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To view this discussion on the web visit https://groups.google.com/d/msg/heroku/-/vWReZqKQJvMJ. 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.
