[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#996570: marked as done (libapache2-mod-proxy-uwsgi: ProxyPass sends wrong PATH_INFO to uwsgi)

Your message dated Mon, 15 Nov 2021 11:02:54 +0100
with message-id <eab846bb-e16a-c7ad-725c-7cb50d2ad77e@uni-paderborn.de>
and subject line Re: Bug#996570: Acknowledgement (libapache2-mod-proxy-uwsgi: ProxyPass sends wrong PATH_INFO to uwsgi)
has caused the Debian Bug report #996570,
regarding libapache2-mod-proxy-uwsgi: ProxyPass sends wrong PATH_INFO to uwsgi
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
996570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996570
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libapache2-mod-proxy-uwsgi
Version: 2.4.38-3+deb10u6
Severity: important

Dear Maintainer,

after installing version 2.4.38-3+deb10u6 our uwsgi webservice did not
work anymore. The apache2 config contains the line

 ProxyPass /networks/v1/ unix:/var/run/uwsgi/networks-api.socket|uwsgi://networks/v1/ retry=0

A request to

 https://server.uni-paderborn.de/networks/v1/name/imt_infra_ntp

used to result in PATH_INFO set to "/name/imt_infra_ntp", so stripping
off the first two directories "/networks/v1/" as set in the config.

Version 2.4.38-3+deb10u6 contains a security fix for setting PATH_INFO,
but it seems to get confused with directories: In our case PATH_INFO
is set to "/v1/name/imt_infra_ntp" which renders our uwsgi webservice
useless.

Thanks for fixing,

Christopher

-- System Information:
Debian Release: 10.11
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-18-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libapache2-mod-proxy-uwsgi depends on:
ii  apache2  2.4.38-3+deb10u5

libapache2-mod-proxy-uwsgi recommends no packages.

libapache2-mod-proxy-uwsgi suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 

Hi,
this was not a bug but only a configuration problem or a misunderstanding of how to configure the module. 

For clearance:
Actually the proxy worker/backend is solely identified by the uwsgi URL, the unix socket part is completely ignored at init time (when the backend URL is registered) and thus when the request URL is mapped to a registered backend URL (to determine which backend backend parameters apply, like timeout or ... connections reuse).
The hostname part of the uwsgi URL is not used for DNS resolution since the endpoint is the unix socket path.
So if you want to run two or more different services on the same host which would result in identical uwsgi URLs, just use different (virtual) hostnames to make them distinguishable. 

Thanks,

Christopher

--
======================================================
    Dipl.-Ing. Christopher Odenbach
    Zentrum fuer Informations- und Medientechnologien
    Universitaet Paderborn
    Raum N5.314
    odenbach@uni-paderborn.de
    Tel.: +49 5251 60 5315
======================================================

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
Reply to: