[
https://issues.apache.org/jira/browse/COUCHDB-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329002#comment-14329002
]
ASF subversion and git services commented on COUCHDB-2601:
----------------------------------------------------------
Commit 2a583cb0dfcd446ae259b272acd58068079c9b52 in couchdb-chttpd's branch
refs/heads/master from [~robertkowalski]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-chttpd.git;h=2a583cb ]
Remove _config route on cluster
In order to avoid users shooting themselves in the foot by using
`/_config/` on a clustered CouchDB with a loadbalancer in front,
we remove it on `15984` - it will be available for single-node-
mode on the backdoor port (`15986`) or for users that are feeling
lucky which want to fire curl requests to every node.
It also allows Fauxton to detect if it is running on a the backdoor
port. Fauxton will - if it gets a 200 instead of a 404 - show the
config-section to the user.
COUCHDB-2601 COUCHDB-2390 COUCHDB-2343
> Config section - remove handler from chttpd
> -------------------------------------------
>
> Key: COUCHDB-2601
> URL: https://issues.apache.org/jira/browse/COUCHDB-2601
> Project: CouchDB
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Database Core, Fauxton
> Reporter: Robert Kowalski
> Assignee: Robert Kowalski
> Priority: Blocker
>
> if Fauxton gets a 404 we are not using the backdoor port which still
> supports `/_config` - this also solves the problem if user are using curl and
> try to change configuration on a clustered CouchDB behind a LB
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
