[pkg-uWSGI-devel] Bug#995368: libapache2-mod-proxy-uwsgi 2.0.14+20161117-3+deb9u4 - duplicated request path

[Sylvain Beucler]

affects 995368 apache2
thanks

@Philippe thank you for the detailed info.

@Moritz bookworm/apache2-2.4.49's behavior currently matches 
uwsgi/stretch's (buggy) behavior, it looks like the upstream patch 
introduced a regression.
(This 2.4.49 release appears to have been tested poorly upstream, that'd 
make the 5th..)

KO: ProxyPass /uwsgi-pp uwsgi://localhost:8001/
OK: ProxyPass /uwsgi-pps/ uwsgi://localhost:8001/
KO: ProxyPassMatch ^/admin uwsgi://localhost:8001/

I'll open a ticket on bz.apache.org.

Cheers!
Sylvain Beucler
Debian LTS Team

On 05/10/2021 14:39, Philippe Accorsi wrote:
> Hi,
> 
> I work on this project https://github.com/tracim/tracim and we saw the 
> problem with the docker images created with files available here 
> https://github.com/tracim/tracim/tree/develop/tools_docker/Debian_Uwsgi/ .
> 
> We create docker images on Debian Stretch and install package 
> libapache2-mod-proxy-uwsgi.
> 
> We use socket connection between Apache and uwsgi. In Apache we use 
> (more detail available directly in repository):
> 
> ProxyPassMatch ^/$ uwsgi://localhost:8081/
> 
> And in uwsgi configuration file we use (more detail available directly 
> in repository):
> 
> plugins = python3
> module = wsgi.web:application
> socket = :8081
> 
> Regards,
> Philippe Accorsi
> 
> Le 05/10/2021 à 13:04, Sylvain Beucler a écrit :
>> Thank you Moritz for forwarding the bug report.
>>
>> Josef, Philippe, can you provide further information, such anas Apache 
>> configuration excerpts, d details about your apache/uwsgi setup?
>>
>> I did not experience issues with my tests using a simple Django 
>> application (cf. https://wiki.debian.org/LTS/TestSuites/uwsgi )
>> so currently I cannot reproduce the problem.
>>
>> Regards,
>> Sylvain Beucler
>> Debian LTS Team
>>
>> On 05/10/2021 10:36, Moritz Mühlenhoff wrote:
>>> reassign 995368 uwsgi
>>> thanks
>>>
>>> Am Fri, Oct 01, 2021 at 04:16:05PM +0200 schrieb Josef Kejzlar, wpj 
>>> s.r.o.:
>>>> I can confirm this regression.
>>>> After unattended security upgrades got applied during the night, all
>>>> our applications stopped working.
>>>>
>>>> There is wrong request path sent to uwsgi server. Some times
>>>> duplicated leading slash.
>>>>
>>>> I would classify this as critical problem, all servers using uwsgi and
>>>> libapache2-mod-proxy-uwsgi stopped working after secuity update.
>>>
>>> Hi Philippe and Josef,
>>> thanks for reporting! This isn't a bug in Apache (source package name
>>> apache2), but got introduced by an update in the uwsgi source package
>>> (which is admittedly confusing since both build Apache modules with 
>>> uwsgi
>>> in their name).
>>>
>>> I'm reassigning the bug and adding the debian-lts list to pick this up.
> -- 
> 
> Bien « collaborativement »,
> 
> Accorsi Philippe
> Administrateur Système et Support Technique
> 
> 
> Le logiciel de collaboration Libre MadeinFrance conçu et édité par Algoo SAS
> e-Mail : philippe.accorsi at algoo.fr <mailto:philippe.accorsi at algoo.fr>
> Tel : 09 72 49 72 20
> Web : www.algoo.fr <https://www.algoo.fr>
>