-
Notifications
You must be signed in to change notification settings - Fork 125
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
Change return code on fail to encode batch secrets #2124
Conversation
55fa376
to
9c182b2
Compare
9c182b2
to
57adba4
Compare
57adba4
to
8e5d2ac
Compare
c115f9b
to
44680ba
Compare
Now when Conjur attempts to encode a batch secrets response into JSON format and encounters an encoding error it will return a 406 status code to the user. This indicates that The given `Accept-Encoding` header is not valid for the retrieved values.
44680ba
to
05230f1
Compare
Code Climate has analyzed commit 05230f1 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 89.1%. View more on Code Climate. |
@alexkalish it only applies to the custom error we added for the batch secrets request endpoint in #1989 (which resolved #1962) we previously added the exception but we didn't rescue it here to return a non-500 error code; this PR fixes that. |
What does this PR do?
Now when Conjur attempts to encode a batch secrets
response into JSON format and encounters an encoding
error it will return a 406 status code to the user.
This indicates that The given
Accept-Encoding
headeris not valid for the retrieved values.
Checklists
Change log
Test coverage
Documentation
README
s) were updated in this PR, and/or there is a follow-on issue to update docs, orAPI Changes