Comment 28 for bug 1677578

@shadowlmd, after reviewing paelzer's comment #26 it is very clear that he made a significant effort to help resolve your report. Looking at paelzer's explanation, he reproduced the root issue in a variety of ways, investigated if this was a known upstream issue, or if known upstream work around existed. In this case this situation should be avoided and corrected via a configurable option.

For this specific issue I also agree that there is no action to take at this time. Later releases have a lower configuration set and changing the behavior in past releases is not an acceptable change for an SRU.