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 <[email protected]>
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

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to