Am 13.08.2014 um 03:12 schrieb Stefan Arentz: > On Aug 5, 2014, at 9:32 AM, [email protected] wrote: > > This sounds like a request scheme issue. > > I ran into this when running the syncserver via ‘make serve’ with an SSL > enabled Nginx proxy in front of it. (So no WSGI). What happens is that Nginx > correctly proxies the requests, but the syncserver thinks it runs on plain > HTTP. And it then uses the wrong request scheme in several checks, which then > fail. This will result in a 401. > > The easiest way to confirm that there is a scheme mismatch is to run your > storage server on plain HTTP. (Make sure you have a correct public_url > setting in syncserver.ini otherwise you will get a audience mismatch error.) > > I wonder if there is a header that can be set to forward the right scheme to > the app. > > S. Hello,
sorry for my late answer, I was some days out of office. I'm using mod_wsgi with Apache from the very beginning. Uwe
_______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
