You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
I think
Content-Type
should beapplication/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 messageThe text was updated successfully, but these errors were encountered: