Support propagating content-type and content-encoding headers as user properties for event hub REST API.
I would like to request that MSFT consider providing access to these properties so that we can use the same standard properties across both HTTP and AMQP. Currently, when using HTTP to send to event hub if you specificy a Content-Type or Content-Encoding those headers are not included with the user properties as previously stated. When using AMQP to send to event hub (and the EventData class) you can explicitly add Content-Type and Content-Encoding properties as user properties, and that works fine such that they are received as user properties.
The problem with this is that it creates the requirement for us (the users of MSFT event hub) to use non-standard custom headers on both the HTTP and AMQP protocol (when standard headers already exist) to achieve a consistent set of user properties to communicate Content-Type and Content-Encoding. For example, I will have to use x-se-content-type and x-se-content-encoding on both HTTP and AMQP since HTTP will not let me use Content-Type and Content-Encoding. I would prefer we be allowed to use the standard Content-Type and Content-Encoding in both HTTP and AMQP protocols.