If I specify "ProxyPass unix:/run/uwsgi/app/site/socket|uwsgi://" (this is inside of a location block, so need for the initial path) I will get "error parsing URL //: Invalid host/port" in the apache logs when I try to access that URL. If I try to change the final part (ie. "|uwsgi://" to "|uwsgi://localhost/"), it just tries to connect through TCP.
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.
If I specify "ProxyPass unix:/run/ uwsgi/app/ site/socket| uwsgi:/ /" (this is inside of a location block, so need for the initial path) I will get "error parsing URL //: Invalid host/port" in the apache logs when I try to access that URL. If I try to change the final part (ie. "|uwsgi://" to "|uwsgi: //localhost/ "), it just tries to connect through TCP.
The problem is fixed (at least for me) by the patch from the mailing list: http:// lists.unbit. it/pipermail/ uwsgi/2015- September/ 008185. html (I also let Debian know about this, so perhaps the fix will come from upstream - https:/ /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 752783# 35).
There is also a workaround: use "vanilla" mod_proxy_http over unix domain sockets:
ProxyPass "/foo" "unix:/ var/run/ uwsgi/foo. socket|http:// uwsgi-uds- foo/"
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.