CloudEvents HTTP transport binding #153
Description
RIG does not yet implement the HTTP transport binding spec.
The receiver of the event can distinguish between the two modes by inspecting the Content-Type header value. If the value is prefixed with the CloudEvents media type application/cloudevents, indicating the use of a known event format, the receiver uses structured mode, otherwise it defaults to binary mode.
Structured mode (content type = application/json)
To be implemented. Currently, we do binary mode here.
Binary mode for JSON (application/cloudevents+json)
That's what we do right now, except for the header, which we expect to be "application/json".