@GrahamcOfBorg test proxy

I'll also note that there are 3 CVE security items mentioned, 2 of which likely apply to us:

https://www-us.apache.org/dist/httpd/CHANGES_2.4

If there is no specific reason against I would suggest be backport this to 18.09.

@peti I just noticed this was merged into staging 21 data ago #54862 but not master. Is apache supposed to go into staging before master? What is the workflow for apache so I don't make this mistake again?

My question regarding backport to 18.09 still stands... do you know why 18.09 hasn't received apache updates in a while?

Thanks!

I just noticed this was merged into staging 21 data ago #54862 but not master. Is apache supposed to go into staging before master?

No, I wouldn't do it that way. I'd merge directly to master.

My question regarding backport to 18.09 still stands... do you know why 18.09 hasn't received apache updates in a while?

We don't update the stable branch unless the new version is backwards-compatible with a high degree of certainty. We don't want to break anyone's installation.

I just noticed this was merged into staging 21 data ago #54862 but not master. Is apache supposed to go into staging before master?

No, I wouldn't do it that way. I'd merge directly to master.

My question regarding backport to 18.09 still stands... do you know why 18.09 hasn't received apache updates in a while?

We don't update the stable branch unless the new version is backwards-compatible with a high degree of certainty. We don't want to break anyone's installation.

@peti thanks for clarification! Apache minor version updates are supposed to be backwards-compatible. Have issues happened in the past which makes you think a minor version update in apache will cause breakage? This seems especially worth while to push into 18.09 because of the 2 CVEs which potentially impact us.