[
https://issues.apache.org/jira/browse/COUCHDB-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790609#comment-13790609
]
Jens Alfke commented on COUCHDB-1479:
-------------------------------------
This seems to have gotten worse in CouchDB 1.4. Now, even if I edit the config
file by hand, the key gets lowercased as soon as CouchDB starts. So the file is
rewritten with the lowercased key, and the config setting doesn't take effect
at all.
So it appears that in CouchDB 1.4 the only way to configure HTTP auth is to go
through Futon (or the REST API) to set this key -- it can't be set in the
config file, and it won't persist across launches.
> Futon config UI won't allow "WWW-Authenticate" option to be added (name is
> lowercased)
> --------------------------------------------------------------------------------------
>
> Key: COUCHDB-1479
> URL: https://issues.apache.org/jira/browse/COUCHDB-1479
> Project: CouchDB
> Issue Type: Bug
> Components: Futon
> Environment: Mac OS X
> Reporter: Jens Alfke
> Priority: Minor
>
> When using the config UI in futon to add a new option, via the "Add a new
> section..." link at the bottom of the page, the name of the option is
> lowercased when written to the .ini file. (For some reason the case is
> preserved when altering the runtime configuration, though, so the problem
> doesn't manifest itself until the next time the server is restarted.)
> This causes trouble when attempting to enable HTTP basic auth by adding a
> "WWW-Authenticate" option (value "Basic") to the [httpd] section. The actual
> data written to the .ini file is:
> [httpd]
> www-authenticate = Basic
> which is not recognized when the server loads its configuration on restart.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
