> We actually haven't been using a process in front of uWSGI until our > internal deployment efforts, which use Repose > (http://www.openrepose.org/). I suppose we hadn't noticed this issue prior > to that because we were using Keystone middleware to form the auth header > info (including combining the XROLES header values). > > At any rate it seems we should be using native http mode for our > deployments, thank you for the correction! > > Thanks, > John
I am not sure this is the right approach (unless i am missing something) Can you paste a full vassal config ? uWSGI speaks various protocols, CGI-based ones (uwsgi, FastCGI, SCGI, mongrel2) and HTTP based ones (http, https) the first ones requires some form of proxy that will need to assemble duplicate headers (nginx for example), while the others need to assemble them (even when behind a proxy). The patch i wrote is for addressing this second issue, but if you are using --socket, you are using the uwsgi protocol (unless you forced another protocol with the --protocol option) so it is your proxy that need to assemble them. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
