Le 26/08/2014 04:37, Ryan Kelly a écrit : > On 25/08/2014 1:08 AM, Adrien CLERC wrote: >> Hi, >> >> I have exactly the same issue. I first reported it in GitHub (see >> https://github.com/mozilla-services/syncserver/issues/37), and then >> realize that I would have more help from the ML :) > OK. Just the ensure everyone's working from the same page, did you try > to nginx config suggestions from my comment on github? > > If you can post your syncserver.ini with passwords/secrets/etc removed, > I'll be happy to sanity-check for any obvious gotchas. > > Ryan > > > Done. You can see the answer at https://github.com/mozilla-services/syncserver/issues/37#issuecomment-53486769 But for ML consistency, I will paste it here: === Duh. It was an issue with gunicorn 0.14.5 I was still using for personal reasons. In this version X-Forwarded-Proto: https is not supported, only X-Forwarded-Protocol: ssl is.
However, when using the latest gunicorn (19.1.1), both headers have the same effect, and work. So I don't know exactly where the issue comes from, I only spent little time checking gunicorn code, but it's a bit pointless. You can mention to use at least this version of gunicorn to make it work :) Thanks for your help, it gave me a clue on what was going wrong. === Adrien _______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
