So when I qualify msg.url string for a 'http request node' it works, but if I put the same string in the given node as a static setting, I get this odd error?
"Warning: msg properties can no longer override set node properties. See bit.ly/nr-override-msg-props"
Looking at the discussion around this error message, I am a bit confused, meaning why would providing a property override as documented in the node documentation be an issue? The node documentation states that msg.url is the way to pass in a URL for the node. So the question is why is overriding a set property now considered bad form? I can think of a few scenarios where setting a 'default' is a valid use case, where the override maybe only used as qualified by flow design.