Expired Key Requests are returned with Content-Type: text/plain; charset=utf-8

[drusellers]

The response data appears to be valid JSON however.

I get the same thing when I add a header Accept: "application/json"

Sample Response Body

{"errorCode":100,"message":"Key not found","cause":"/1a54dfaa-28c7-4180-b4e9-970c41342a39","index":196}

[kelseyhightower]

@drusellers Thanks for reporting this issue. I'm going to try and quickly reproduce using etcd v0.2.0.

[kelseyhightower]

I was able to reproduce this issue on etcd v0.2.0 by running the following command:

curl -i http://10.0.1.150:4001/v2/keys/1a54dfaa-28c7-4180-b4e9-970c41342a39 \
-H 'Accept: application/json'

HTTP/1.1 404 Not Found
Content-Type: text/plain; charset=utf-8
X-Etcd-Index: 2
Date: Thu, 23 Jan 2014 13:05:15 GMT
Content-Length: 102

{"errorCode":100,"message":"Key not found","cause":"/1a54dfaa-28c7-4180-b4e9-970c41342a39","index":2}

[drusellers]

I found this again with 'Compare and Swap' and when doing 'Compare and Delete'

[drusellers]

Ping - i'm pretty new to go - but would this be considered an easy fix to provide?

[philips]

@drusellers This should be fixed in master and will appear in 0.4.2. If you can test and confirm that would be great.

[drusellers]

yup. fixed.

On Fri, May 30, 2014 at 8:27 PM, Brandon Philips notifications@github.com
wrote:

Closed #469 #469.

—
Reply to this email directly or view it on GitHub
#469 (comment).