Your help is much appreciated Robert!

We'll move over to using your suggested patch and config mods. Do you think 
your patch might be included with an upcoming release?

Thanks,
John

________________________________________
From: [email protected] [[email protected]] on behalf of 
Roberto De Ioris [[email protected]]
Sent: Monday, March 31, 2014 8:59 AM
To: uWSGI developers and users list
Subject: Re: [uWSGI] Multiple request headers with same name

> Here is our vassal config (for our public process):
>
> [uwsgi]
> socket = :9311
> protocol = http
> processes = 1
> lazy = true
> vacuum = true
> no-default-app = true
> memory-report = true
> plugins = python
> paste = config:/etc/barbican/barbican-api-paste.ini
>
> So it does seem that the 'protocol' line should be selecting http mode
> then, in which case your patch could work for our non-nginx deployments.
>
> BTW, we launch the app this way:
>
> uwsgi --master --die-on-term --emperor /etc/barbican/vassals --logto
> /var/log/barbican/barbican-api.log --stats localhost:9314
>
> Note that we haven't attempted to tune uWSGI for performance yet. :)
>
> Thanks,
>

ok, yes, you can combine --socket + --protocol in a single

--http-socket <address>

option, and with the patch you should solve your issue. I tend to suggest
--http-socket to maintain more control over protocols, so in the future
you could use a uwsgi socket for rpc (as an example) and an http one for
webserver integration (both in the same instance)

(just one note about --lazy, it is here only for backward compatibility,
if you only need non-preforked app loading use --lazy-apps that does not
change reloading mechanisms, more on this here:
http://uwsgi-docs.readthedocs.org/en/latest/articles/TheArtOfGracefulReloading.html)

--
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

Reply via email to