Can't use server.subscribe for messages via sidecar

[micro]

Can't use server.subscribe for messages via sidecar

[asim]

Easiest fix would probably be to have the sidecar accept a broker.Message rather than filling in the body of a broker.Message with whatever's passed in. It's a breaking change though so it affects anyone already using the sidecar. I'll have to give it some thought.

[bkleef]

@asim any thoughts on this?

[asim]

The issue is because of this https://github.com/micro/micro/blob/master/internal/handler/broker.go#L56. I'm open to suggestions on a fix, otherwise I'm not touching it for the moment.

[asim]

An easy solution would perhaps be to take Content-Type from the initial request and use that as the basis for any messages published.

[asim]

Here's a PR to fix it #70. When you connect to the /broker endpoint on the sidecar you specify the content-type header which will then be used for all publications. If a content-type is not specified then it will default to application/json.

It's a bit of a hack of a fix as it doesn't actually allow you to set your own headers.

[asim]

Merged PR.