Comment 22 for bug 1337349

Note that the "new config option" approach (which I think is the right choice to fix this issue) is not really backportable to stable/*, so it's not appropriate for an OSSA patch.

But then I think any fix for this would introduce a behavior change that is not welcome in stable/* -- so we should probably just fix this in master, make the patch available for backport for those who wish to carry it in their deployments, and (maybe) issue an OSSN about it to raise awareness around the issue.

Thoughts?