Skip to content

/application/env/{propertyName} returns 200 for a property that does not exist #10179

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

Closed
snicoll opened this issue Sep 6, 2017 · 1 comment
Closed
Assignees
Labels
type: regression A regression from a previous release
Milestone

Comments

@snicoll
Copy link
Member

snicoll commented Sep 6, 2017

If you query the env endpoint for a property and that property doesn't exist (Environment#containsProperty returns false), the web endpoint returns a 200.

We could return null in the endpoint method to make it return a 404 instead but we'd lose the information about which property sources are active.

@snicoll snicoll added type: regression A regression from a previous release and removed type: bug A general bug labels Sep 20, 2017
@snicoll snicoll added this to the 2.0.0.M5 milestone Sep 20, 2017
@wilkinsona
Copy link
Member

See also #10178

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: regression A regression from a previous release
Projects
None yet
Development

No branches or pull requests

2 participants