Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proper Content-Type #39

Closed
crodas opened this issue Nov 12, 2013 · 0 comments
Closed

Proper Content-Type #39

crodas opened this issue Nov 12, 2013 · 0 comments

Comments

@crodas
Copy link

crodas commented Nov 12, 2013

curl "localhost:8086/db/foo/series?u=root&p=root&q=SELECT%20*%20FROM%20foobar%3B" -v

* About to connect() to localhost port 8086 (#0)
*   Trying ::1...
* connected
* Connected to localhost (::1) port 8086 (#0)
> GET /db/foo/series?u=root&p=root&q=SELECT%20*%20FROM%20foobar%3B HTTP/1.1
> User-Agent: curl/7.25.0 (x86_64-suse-linux-gnu) libcurl/7.25.0 OpenSSL/1.0.1e zlib/1.2.7 libidn/1.25 libssh2/1.4.0
> Host: localhost:8086
> Accept: */*
> 
< HTTP/1.1 200 OK
< Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept
< Access-Control-Allow-Methods: GET, POST, PUT, DELETE
< Access-Control-Allow-Origin: *
< Access-Control-Max-Age: 2592000
< Date: Tue, 12 Nov 2013 19:01:36 GMT
< Content-Length: 2
< Content-Type: text/plain; charset=utf-8
< 
* Connection #0 to host localhost left intact
[]* Closing connection #0

I think Content-Type should be application/json. It does follow a pattern though (which makes total sense to me), if request is not 2xx, the text (which is text/plain) is the error message

jvshahid pushed a commit that referenced this issue Aug 12, 2014
Blocking the transportation when the server will stepdown
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant