You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Prakash Babu T (JIRA)" <ji...@apache.org> on 2014/02/28 16:06:21 UTC

[jira] [Created] (COUCHDB-2180) Issue replicating from behind firewall using http_proxy

Prakash Babu T created COUCHDB-2180:
---------------------------------------

             Summary: Issue replicating from behind firewall using http_proxy
                 Key: COUCHDB-2180
                 URL: https://issues.apache.org/jira/browse/COUCHDB-2180
             Project: CouchDB
          Issue Type: Task
      Security Level: public (Regular issues)
          Components: Replication
            Reporter: Prakash Babu T


Hi,

I am setting up a local repository for npm. The couchdb sync fine while not behind a firewall. But our hosted replication server is in a zone where we need to use http_proxy for hitting the external sites.

For couch db replicate I tried with proxy settings similar to given below, but all the combinations that I tried did not work.. 

These are the several options that I tried. Could someone please help to fix this? or let me know if I am missing something.

1.
curl -x http://<proxyurl>:80 -X POST http://10.137.115.211:5984/_replicate -d@npmRegistry.json -H "Content-Type: application/json"

cat npmRegistry.json 
{"source":"http://isaacs.iriscouch.com/registry", "target":"registry", "continuous":true, "create_target":true}

2. 

curl -x http://<proxyurl>:80 -X POST http://10.137.115.211:5984/_replicate -d '{"source":"http://isaacs.iriscouch.com/registry/", "target":"registry", "create_target":true}' -H "Content-Type: application/json" 

3. 

curl  -X POST http://10.137.115.211:5984/_replicate -d '{"source":"http://isaacs.iriscouch.com/registry/", "target":"registry", "create_target":true, "proxy":"http://<proxyurl>:80" }' -H "Content-Type: application/json" 

4. I tried from the web interface of couched

5. I tried with the npm replicate application, after setting up npm set config http-proxy

All these options did not work.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)