> Though projections on “.http” got removed two years ago, we confusingly saw A LOT calls of the form "<action>.http/foo/bar”. Research showed that those customers are accessing the “foo/bar” section of the path via the "message.__ow_path" property in their action code to be used as additional parameters.
This is necessary if you want to implement more general APIs and the reason to remove projections from .json etc is so that you can do the same. With the current behavior you have actions that will behave differently when accessed with .http and .json and that's a mistake and very confusing. -r
