Problems: - 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. I would really prefer unix sockets to TCP since they can be secured better.
- I tried to change over to TCP, however it seems that mod_proxy_uwsgi doesn't parse the port number from the URL. Ie. even if I specify "ProxyPass uwsgi://127.1.0.1:3001/", it will try to connect on port 3031 which seems to be the default port [1]. A quick glance at the code seems to indicate that that ie *does* parse the port part [2], so I'm not sure what goes wrong there. Using multiple ports would be essential (or getting unix sockets working) since I want to run multiple apps / domains on the server with uwsgi (I also tried putting the proxy pass outside of the Location block and adding the path as shown in the documentation - ie. "ProxyPass / uwsgi://127.1.0.1:3032/") but it still doesn't seem to parse the port number and uses the default port. Regards, Attila Balazs (Grey Panther) [1] https://github.com/unbit/uwsgi/blob/master/apache2/mod_proxy_uwsgi.c#L54 [2] https://github.com/unbit/uwsgi/blob/master/apache2/mod_proxy_uwsgi.c#L75
