You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@avro.apache.org by "Martin Mucha (JIRA)" <ji...@apache.org> on 2019/04/13 08:42:00 UTC

[jira] [Commented] (AVRO-488) Invalid HTTP Content-Type

    [ https://issues.apache.org/jira/browse/AVRO-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16816869#comment-16816869 ] 

Martin Mucha commented on AVRO-488:
-----------------------------------

nine years guys.

You are ruining specifications, you understand that, right? This should be resolved at least in mediocre acceptance of invalid solution. But not being able to clearly decide is just creating specification mess in M$ style.

> 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
(v7.6.3#76005)