Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 31 Jan 2021 05:42:57 +0000
From:      bugzilla-noreply@freebsd.org
To:        apache@FreeBSD.org
Subject:   [Bug 250845] www/apache24: mod_proxy_uwsgi doesn't use default port of uwsgi:// scheme.
Message-ID:  <bug-250845-16115-5jWZdZWcXS@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-250845-16115@https.bugs.freebsd.org/bugzilla/>
References:  <bug-250845-16115@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250845

--- Comment #2 from nork@ninth-nine.com ---
Hi Bernard,


> Looks like there isn't something like a default port for uWSGI (at least =
looking at the uWSGI docs I don't see it). Guess this is why it's not defin=
ed in the code.

Yes. But I don't know why.

> Guess this is why it's not defined in the code. The documentation clearly=
 contains the port for all configurations. Perhaps makes sense to submit pa=
tch to add an admonition "NOTE: You must use a port number in your ProxyPas=
s"  instead?

That's fine, but "NOTE: You must use a port number exclude 3031 in your
ProxyPass".  In this time, apache24 reports a error like following setting:

ProxyPass / uwsgi://127.0.0.1/
ProxyPass / uwsgi://127.0.0.1:3031/

And also, unix domain "with port number" causes a error like following sett=
ing:

ProxyPass / unix:/tmp/.uwsgi.sock|uwsgi://127.0.0.1:3031/
ProxyPass / unix:/tmp/.uwsgi.sock|uwsgi://127.0.0.1:3032/

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-250845-16115-5jWZdZWcXS>