I do not know for certain. One user on the upstream bug mentions it can't be backported because of an API compat issue, but if there's one present I'm sure not seeing it. The define is entirely contained within that header file. The only thing I would think it could affect would be external modules built against mod_proxy.h
Hi Robie,
I do not know for certain. One user on the upstream bug mentions it can't be backported because of an API compat issue, but if there's one present I'm sure not seeing it. The define is entirely contained within that header file. The only thing I would think it could affect would be external modules built against mod_proxy.h
root@apache2- mod-proxy- length- xenial: ~/apache2- 2.4.18# grep -R 'PROXY_ WORKER_ MAX_NAME_ SIZE' * proxy/mod_ proxy.h: #define PROXY_WORKER_ MAX_NAME_ SIZE 96 proxy/mod_ proxy.h: #define PROXY_BALANCER_ MAX_NAME_ SIZE PROXY_WORKER_ MAX_NAME_ SIZE proxy/mod_ proxy.h: char name[PROXY_ WORKER_ MAX_NAME_ SIZE]; proxy/mod_ proxy.h: char uds_path[ PROXY_WORKER_ MAX_NAME_ SIZE]; /* path to worker's unix domain socket if applicable */ mod-proxy- length- xenial: ~/apache2- 2.4.18# grep -R 'PROXY_ BALANCER_ MAX_NAME_ SIZE' * proxy/mod_ proxy.h: #define PROXY_BALANCER_ MAX_NAME_ SIZE PROXY_WORKER_ MAX_NAME_ SIZE proxy/mod_ proxy.h: char name[PROXY_ BALANCER_ MAX_NAME_ SIZE]; proxy/mod_ proxy.h: char sname[PROXY_ BALANCER_ MAX_NAME_ SIZE];
modules/
modules/
modules/
modules/
root@apache2-
modules/
modules/
modules/