On Sat, Dec 23, 2017 at 3:53 PM, Stefan Eissing <stefan.eiss...@greenbytes.de> wrote: > > I think this really is a bug in our runtime. The flag was invented > just for precaution, in case a module would rely on the no-copy > behaviour. That is really close to saying: we will not fix > any more bugs in 2.4.x as someone could rely on it.
I would be fine with duplicating/merging every server config by default, even when no module directive is specified, the risk is that some (third party) merger functions might not do the right thing when called in this situation, and could break. Too much caution possibly...
