public interface RequestMetaData
HTTP is a very "special" transport: There are a number of places in OSB code that need to do processing of HTTP-specific metadata, e.g. 1) security (custom authentication) 2) several handlers in service handler chain, e.g. REST-related 3) pipeline runtime (REST branch) 4) Routing options Due to current build order dependencies, HTTP transport gets built pretty late, which leaves the above pieces of code no choice but to use reflection in order to manipulate HTTP-specific metadata. The goal of this interface is to instead provide some common ground for all such usages, thus making it less error-prone and easier to maintain. This is not a public interface that should be exposed to customers