You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@htrace.apache.org by "Colin Patrick McCabe (JIRA)" <ji...@apache.org> on 2015/01/05 17:57:34 UTC
[jira] [Resolved] (HTRACE-52) FIgure out content-type handling in
JSON API
[ https://issues.apache.org/jira/browse/HTRACE-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colin Patrick McCabe resolved HTRACE-52.
----------------------------------------
Resolution: Fixed
Fix Version/s: 3.2.0
> FIgure out content-type handling in JSON API
> --------------------------------------------
>
> Key: HTRACE-52
> URL: https://issues.apache.org/jira/browse/HTRACE-52
> Project: HTrace
> Issue Type: Bug
> Affects Versions: 3.2.0
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Fix For: 3.2.0
>
> Attachments: HTRACE-52.001.patch
>
>
> We should figure out how to handle content-type in the JSON API. We should definitely be setting {{Content-Type}} as {{application/json}} when writing data.
> I guess a secondary question is whether the server should reject calls to APIs like {{/writeSpan}} if Content-Type is set incorrectly. I'm not sure if this adds any value... thoughts?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)