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

HTTP API should return 503 when sealed #213

Closed
ianunruh opened this issue May 17, 2015 · 2 comments
Closed

HTTP API should return 503 when sealed #213

ianunruh opened this issue May 17, 2015 · 2 comments

Comments

@ianunruh
Copy link
Contributor

In the API docs, it is specified that when the Vault is sealed, the API will return a 503 Service Unavailable. As of 0.1.2 however, it returns a 500 Internal Server Error with the error message Vault is sealed.

https://vaultproject.io/docs/http/index.html
@ianunruh ianunruh changed the title HTTP API should return 503 if Vault is sealed HTTP API should return 503 when sealed May 17, 2015
@armon armon added the bug label May 18, 2015
@armon
Copy link
Member

armon commented May 18, 2015

Tagged as bug

@ianunruh ianunruh mentioned this issue May 19, 2015
Merged
armon added a commit that referenced this issue May 19, 2015
@armon
Merge pull request #225 from ianunruh/fix/gh-213
512bf8f 
HTTP should return 503 when sealed
@ianunruh
Copy link
Contributor Author

Fixed in #225

rajanadar added a commit to rajanadar/VaultSharp that referenced this issue Aug 28, 2016
@rajanadar
absorbing new status codes and fields.
486f7bb 
working towards parity with hashicorp/vault#213
This was referenced Feb 19, 2022
Open
Open
@terrorizer1980 terrorizer1980 mentioned this issue Jul 4, 2023
Open
@leftrightleft leftrightleft mentioned this issue Jul 5, 2023
Open
@terrorizer1980 terrorizer1980 mentioned this issue Nov 30, 2023
Open
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

No branches or pull requests
2 participants
@armon @ianunruh