incubator-couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Shorin (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (COUCHDB-1215) Improve _config error handling by validating certain (if not all) values based on their keys
Date Tue, 02 Jul 2013 00:03:20 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alexander Shorin closed COUCHDB-1215.
-------------------------------------

    Resolution: Duplicate

Closing in favour of COUCHDB-1446 since it handles this problem more widely.
                
> Improve _config error handling by validating certain (if not all) values based on their
keys
> --------------------------------------------------------------------------------------------
>
>                 Key: COUCHDB-1215
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1215
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Futon, HTTP Interface
>    Affects Versions: 1.1
>            Reporter: Benjamin Young
>            Priority: Minor
>
> When saving values via Futon or the HTTP API, it's easy to put in values that are invalid
and could make CouchDB unbootable. Some level of validation here would save the day in most
cases or the disposal of the incorrect values with a log message (rather than preventing startup).
> In my case, I'd added just <<"http://google.com/">> to the value of the _google
key in the httpd_global_handlers section and that prevented CouchDB from starting. The ever
fabulous Paul Davis pointed out my error and it was "easy enough" to fix by altering the value
in the .ini file to be the correct value...which is: {couch_httpd_proxy, handle_proxy_req,
<<"http://www.google.com">>}
> In the case of these httpd_global_handlers a simple check that it's an Erlang tuple with
at least two terms would be a simple check that would have kept my CouchDB instance up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message