Upvoting this as we would like to see a subset of this request implemented please, namely that notification callouts which receive any 2xx status code should be treated as successful, as per RFC2616, not just 200 (OK). We've worked around this for the time being, by explicitly returning 200 where our API framework would normally respond with 204 (No Content), but it would be great if this could be done so that we could remove that work-around. Thanks to Jean-Christophe Duwer for answering the support ticket I raised about this and pointing me towards this idea to upvote and comment on. Cheers, Chris
... View more
