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

Improve error handling for 400 #96

Closed
dzmitry-lahoda opened this issue May 22, 2020 · 1 comment · Fixed by #98
Closed

Improve error handling for 400 #96

dzmitry-lahoda opened this issue May 22, 2020 · 1 comment · Fixed by #98

Comments

@dzmitry-lahoda
Copy link

dzmitry-lahoda commented May 22, 2020

I get next error:

HTTP/1.1 400 Bad Request
Server: nginx/1.12.2
Date: Fri, 22 May 2020 17:12:34 GMT
Content-Type: application/json
Content-Length: 99
Connection: keep-alive

{"statement_id":0,"error":"query not allowed: accessing database \"foobarbaz\" is not allowed"}

And see:
image

Expected:

If you cannot parse resonces, at least provide it error code and inner text

@mvadu
Copy link
Contributor

mvadu commented May 23, 2020

I will work on it.

@mvadu mvadu closed this as completed in #98 Aug 11, 2020
mvadu added a commit that referenced this issue Aug 11, 2020
Move to multi-target project. Keep one Nuget package going forward.
Fixed #96, Fixed #97
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants