[
https://issues.apache.org/jira/browse/COUCHDB-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042252#comment-16042252
]
Denis Washington commented on COUCHDB-3172:
-------------------------------------------
[~wohali] Thank you for the pointer, although the prospect of having to
recompile CouchDB in order to integrate this doesn't seem very compelling
maintenance-wise.
Anyway, the point stands that a documented feature (proxy handlers) is
currently broken. Is this just a case of something that just needs to be
implemented (presumably in chttpd?), or is there something about it that is
conceptually at odds with the cluster model?
> httpd_global_handlers proxy on main cluster interface
> -----------------------------------------------------
>
> Key: COUCHDB-3172
> URL: https://issues.apache.org/jira/browse/COUCHDB-3172
> Project: CouchDB
> Issue Type: Bug
> Reporter: Wiktor Obrębski
>
> couch_httpd_proxy looks like no working in main cluster 5984 interface in
> CouchDB 2.0.
> {code:title=config}
> [httpd_global_handlers]
> _fti = {couch_httpd_proxy, handle_proxy_req, <<"http://127.0.0.1:5985";>>}
> {code}
> it work only when I use direct node port (5986).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
