[pkg-uWSGI-devel] Bug#752783: I think I found the solution / workaround

[Jonas Smedegaard]

Quoting Attila-Mihály Balázs (2015-10-01 19:38:48)
> For the first problem (unix sockets not working with mod_proxy_uwsgi), 
> the following patch solved the problem for me: 
> http://lists.unbit.it/pipermail/uwsgi/2015-September/008185.html
>
> Until that lands, I found the following work-around:
> - change "socket" to "http-socket" in uwsgi.ini (so that uwsgi speaks 
> http instead of the uwsgi protocol)
> - use "vanilla" mod_proxy_http over unix domain sockets:
>
> ProxyPass "/foo" "unix:/var/run/uwsgi/foo.socket|http://uwsgi-uds-foo/"
>
> - the problem with the port not being parsed when TCP was being used was 
> fully PEBCAK - I had a different virtualhost config getting activated 
> than the one I believed was getting activated. mod_proxy_uwsgi properly 
> parses and uses the port for TCP connections.

Nice work.  Thanks for sharing!


> PS. Apparently, if you have multiple instances of uwsgi you want to 
> connect to, you need to specify different names for them (ie. 
> "http://uwsgi-uds-foo/", "http://uwsgi-uds-bar/", etc), having just 
> different paths to the sockets will not work.

Please try work with upstream to improve their documentation regarding 
details like that.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-uwsgi-devel/attachments/20151001/6a1007a4/attachment.sig>