Comment 38 for bug 1581864

Thanks Athos for flagging this,
you are right if we do not fix it now for Bionic it won't be fixed at all.
But OTOH no one except internal people have revisited this for ages, and being only cosmetic (the service is up and running fine) this won't make the last minute (in the release lifecycle) SRU acceptance especially given the discussions around how it was resolved.

Upstream isn't very happy with the resolution [1] and I'd more lean to even challenge/reconsider if we might drop this in new versions - this is 3 years old maybe it is a non issue nowadays.

If someone thinks this is a wrong assumptions please speak up, outline why it is important to be fixed in Bionic in a way that will most likely also convince the SRU team to accept the risk.
Otherwise I'd call this a win't fix for Bionic too.

[1]: https://trac.nginx.org/nginx/ticket/1897