couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-2601) Config section - remove handler from chttpd
Date Fri, 20 Feb 2015 14:54:13 GMT


ASF subversion and git services commented on COUCHDB-2601:

Commit 2a583cb0dfcd446ae259b272acd58068079c9b52 in couchdb-chttpd's branch refs/heads/master
from [~robertkowalski]
[;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.


> Config section - remove handler from chttpd
> -------------------------------------------
>                 Key: COUCHDB-2601
>                 URL:
>             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

View raw message