You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/02/19 21:35:11 UTC
[jira] [Commented] (COUCHDB-2601) Config section - remove handler
from chttpd
[ https://issues.apache.org/jira/browse/COUCHDB-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14328074#comment-14328074 ]
ASF GitHub Bot commented on COUCHDB-2601:
-----------------------------------------
GitHub user robertkowalski opened a pull request:
https://github.com/apache/couchdb-chttpd/pull/25
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
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/robertkowalski/couchdb-chttpd 2601-remove-config-handler
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-chttpd/pull/25.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #25
----
commit 2a583cb0dfcd446ae259b272acd58068079c9b52
Author: Robert Kowalski <ro...@apache.org>
Date: 2015-02-19T20:21:25Z
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)