Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blacklist some config sections from HTTP PUT/DELETE operations #914

Merged
merged 1 commit into from
Oct 25, 2017

Conversation

wohali
Copy link
Member

@wohali wohali commented Oct 25, 2017

Covers clustered and node-local ports.

Includes JS test for clustered port.

@wohali wohali requested review from janl and rnewson October 25, 2017 16:36
@wohali wohali force-pushed the blacklist-config-sections branch 2 times, most recently from 8ff84f4 to ea10bd3 Compare October 25, 2017 19:30
@wohali wohali removed the request for review from rnewson October 25, 2017 19:52
@wohali wohali merged commit 82635ef into master Oct 25, 2017
@wohali wohali deleted the blacklist-config-sections branch October 25, 2017 21:48
kxepal added a commit to kxepal/couchdb that referenced this pull request Oct 25, 2017
kxepal added a commit to kxepal/couchdb that referenced this pull request Oct 26, 2017
kxepal added a commit to kxepal/couchdb that referenced this pull request Oct 26, 2017
janl pushed a commit that referenced this pull request Oct 31, 2017
@ondra-novak
Copy link

Is there some way to remove blacklist? I am heavily using os_daemons to start/stop daemons by http

@kxepal
Copy link
Member

kxepal commented Nov 12, 2017

@ondra-novak
Suddenly, no - it's a security measurement. However, for 2.x you still can manage os_daemons in runtime by modifying config file and reloading it via /_config/_reload, IIRC. You can setup special externals which will do that for you. But, it's all for your own risk.

@ondra-novak
Copy link

ondra-novak commented Nov 12, 2017

OK, so I will need to put some http server there....

<irony>oh boy, please make things more complicated next time</irony>

@wohali
Copy link
Member Author

wohali commented Nov 12, 2017

We know this change is frustrating for your specific use case, but there is a good reason for this change.

Again, insulting members of our project team doesn't help anyone. I ask you again to abide by our Code of Conduct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants