[
https://issues.apache.org/jira/browse/AVRO-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17201414#comment-17201414
]
Ryan Skraba commented on AVRO-488:
----------------------------------
Hello! What would be the impact of just switching all of the references to a
legal media type in the next major release? Would it break load balancers,
front-ends, application servers? If there is an impact, what can we do to help
existing applications make the transition to a legal media type?
I haven't read all the relevant RFCs entirely -- what would be the appropriate
media type in 2020? {{application/x.avro}} and {{application/x.avro+json}} ?
I suspect the priority is "minor" exactly because we've lived with and worked
around this for the last ten years! But there's no reason not to fix it if
it's non-standard and causing confusion.
> 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)
