[
https://issues.apache.org/jira/browse/COUCHDB-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233253#comment-13233253
]
Jason Smith commented on COUCHDB-1446:
--------------------------------------
That is a pretty exciting idea. I find two things very appealing:
1. Belt-and-suspenders: validate the input as much as reasonable, but also
don't use bad data if it's in there (because a user could always edit the .ini;
or just generally speaking, one subsystem shouldn't trust the other).
2. Extend the config system to be more general and more useful.
However IMO this ticket addresses a pretty restricted scope: input validation
in the 1.2.x codebase. Normally I wouldn't nitpick except that this issue came
from a real-world user not particularly steeped in CouchDB culture or
community. It has street cred.
Can we get a conversation about the broader feature set in CouchDB 3000, and
let that inform a more modest quick-fix in the 1.2.x code line?
> Config settings input validation
> --------------------------------
>
> Key: COUCHDB-1446
> URL: https://issues.apache.org/jira/browse/COUCHDB-1446
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core
> Affects Versions: 1.2
> Reporter: Jason Smith
> Assignee: Jason Smith
> Priority: Minor
> Labels: config
>
> Today I received a bug report from a user who thought CouchDB might be
> relaxing and evaluate an arithmetic expression in the config. (That makes
> sense, since it seems to evaluate erlang terms elsewhere.)
> https://getsatisfaction.com/iriscouch/topics/my_couchdb_is_broken_after_putting_a_badarg_for_a_configuration_value
> It would be nice for CouchDB to validate config input, particularly when bad
> values permanently take it offline. (In this case, it returns 500 for all
> subsequent requests.)
> IMO, a good bang-for-buck is to have three basic value types:
> 1. String
> 2. Erlang tuple
> 3. Integer
> And each setting knows what type it must be.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
