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? [1] http://uwsgi-docs.readthedocs.org/en/latest/HTTP.html#the-uwsgi-http-https-router [2] http://uwsgi-docs.readthedocs.org/en/latest/Options.html?highlight=http#http Thank you again! John ________________________________________ From: [email protected] [[email protected]] on behalf of Roberto De Ioris [[email protected]] Sent: Monday, March 31, 2014 3:30 AM To: uWSGI developers and users list Subject: Re: [uWSGI] Multiple request headers with same name > Hello Robert, > > We are using falcon as our web framework. Please see the issue thread here > for more context: https://github.com/racker/falcon/issues/224 > > Thank you, > John This patch adds support for combining headers when in native http mode: https://github.com/unbit/uwsgi/commit/8a032b41ec356f85104cc856922a18f4eee9b407 (i do not know if it is your case, but this should be definitely fixed in http parsers, patch for http router will follow soon) -- 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
