I just had a look at the proposed package and it fixes the issue for me.
To test the patch I followed the steps as explained in the bug description, first with apache2/xenial-updates,now 2.4.18-2ubuntu3.14 amd64 and the issue could be reproduced with the command
After upgrading the package to apache2/xenial-proposed,now 2.4.18-2ubuntu3.15 amd64 and running the same curl command as before, the output was the expected real IP addresss of the client.
Hello Robie,
I just had a look at the proposed package and it fixes the issue for me. xenial- updates, now 2.4.18-2ubuntu3.14 amd64 and the issue could be reproduced with the command
To test the patch I followed the steps as explained in the bug description, first with apache2/
$ curl 192.168.1.129/test -H 'X-Forwarded-For: 1.1.1.1'
> 1.1.1.1
After upgrading the package to apache2/ xenial- proposed, now 2.4.18-2ubuntu3.15 amd64 and running the same curl command as before, the output was the expected real IP addresss of the client.
$ curl 192.168.1.129/test -H 'X-Forwarded-For: 1.1.1.1'
> 192.168.1.100
Regards