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 ________________________________________ From: [email protected] [[email protected]] on behalf of Roberto De Ioris [[email protected]] Sent: Monday, March 31, 2014 8:28 AM To: uWSGI developers and users list Subject: Re: [uWSGI] Multiple request headers with same name > Wow, thanks Robert! > > We are currently using emperor/vassal mode with the 'socket' option. It > seems we should instead use the '--http' option (using either native http > embedded or standalone modes) per sections [1] and [2] ? > > Also do you know when this patch might be released? Hmm, nope, with --socket you should have a webserver on front, and it must combine headers by itself. Which webserver before your uWSGI instances ? -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
