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.

Sign up for GitHub

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

Jump to bottom

Handle 401 status code before checking content type. #38

Closed
ewoutp opened this issue Jun 8, 2017 · 0 comments · Fixed by #39
Closed

Handle 401 status code before checking content type. #38

ewoutp opened this issue Jun 8, 2017 · 0 comments · Fixed by #39

Comments

@ewoutp
Copy link
Contributor

ewoutp commented Jun 8, 2017

The server will return a content type of text/plain in certain cases where the caller has no access to an object. Currently this results in an Invalid content type error.
Instead it should result in an "you have no access" error.

See also #35 & #36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Convert 401 text/plain response to proper ArangoError arangodb/go-driver
1 participant
@ewoutp