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

Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2015/06/23 23:53:43 UTC

[jira] [Resolved] (CALCITE-765) RPC server returns JSON data with Content-Type set to text/html

     [ https://issues.apache.org/jira/browse/CALCITE-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde resolved CALCITE-765.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.4.0-incubating

Fixed in http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/d559bacf.

Thanks Lukas!

> RPC server returns JSON data with Content-Type set to text/html
> ---------------------------------------------------------------
>
>                 Key: CALCITE-765
>                 URL: https://issues.apache.org/jira/browse/CALCITE-765
>             Project: Calcite
>          Issue Type: Improvement
>    Affects Versions: 1.4.0-incubating
>            Reporter: Lukas Lalinsky
>            Assignee: Julian Hyde
>            Priority: Minor
>             Fix For: 1.4.0-incubating
>
>
> The server currently always sets Content-Type to text/html, even though it's actually returning JSON data. That makes it hard to distinguish JSON response from a Jetty-generated error page. I suggest changing it to application/json (RFC 4627). I'm experimenting with writing a Python client for the RPC and I'd like to generate better exceptions than "something failed". How to handle error in the RPC is a discussion for another ticket, but this seems like the first obvious step.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)