[
https://issues.apache.org/jira/browse/AVRO-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17200632#comment-17200632
]
Rinke commented on AVRO-488:
----------------------------
Another year on... the link to the [de-facto standard
|https://docs.spring.io/spring-cloud-stream/docs/Brooklyn.RELEASE/reference/html/contenttypemanagement.html#_converters_with_schema_support]by
spring.io is not consistent either, as the examples use {{avro/binary}} .
IMO this should really be resolved, and pending IANA registration of a proper
mimetype, I'd vote for the suggestions by [~amichai] in the original of this
message.
And, why is this a `minor` priority? Sure, it's a minor change, but the
priority seems to be pretty high. Fully agree with [~alfonz] on that point.
> Invalid HTTP Content-Type
> -------------------------
>
> Key: AVRO-488
> URL: https://issues.apache.org/jira/browse/AVRO-488
> Project: Apache Avro
> Issue Type: Bug
> Components: spec
> Reporter: Amichai Rothman
> Priority: Minor
>
> AIUI "avro/binary" is not a legal HTTP content type. It should be something
> more like "application/x-avro-binary", or registered with IANA as
> "application/avro-binary".
> Also, perhaps the spec should mention an "application/avro-json" type as well?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
