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

Handle non-JSON 404 Response on Session.renew PUT request #36

Open
rodoyle opened this issue Mar 3, 2020 · 0 comments
Open

Handle non-JSON 404 Response on Session.renew PUT request #36

rodoyle opened this issue Mar 3, 2020 · 0 comments
Labels

Comments

@rodoyle
Copy link
Contributor

rodoyle commented Mar 3, 2020

When Session::renew yields a 404 response Response: '404 Not Found' for http://localhost:8500/v1/session/renew/f933ddd8-c5a6-5d7e-898e-95fc8aebaadb? to a PUT request,
the client will return the following JSON parse error
Error(Msg("Failed to parse JSON"), State { next_error: Some(Error(Json(Error("expected value", line: 1, column: 1)))), backtrace: InternalBacktrace { backtrace: None } }

This is likely because the error responses are not valid JSON.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants