Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <1600427347.1259649022235.JavaMail.jira@brutus>
Date: Tue, 1 Dec 2009 06:30:22 +0000 (UTC)
From: "Mark Hammond (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Commented: (COUCHDB-587) provide peer port information to
 externals
In-Reply-To: <1513945334.1259648480611.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COUCHDB-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784083#action_12784083 ] 

Mark Hammond commented on COUCHDB-587:
--------------------------------------

Oh sorry - I misunderstood the comments in 393 to imply couchdb doesn't actually *know* the port anywhere convenient.

> provide peer port information to externals
> ------------------------------------------
>
>                 Key: COUCHDB-587
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-587
>             Project: CouchDB
>          Issue Type: New Feature
>            Reporter: Mark Hammond
>
> When requests are made to an external, couch DB provides a 'peer' item in the request info with the address of the couchdb instance (eg, 127.0.0.1).  CouchDB should also provide the port on this address, so externals can reliably make requests back to couch.
> The comments in COUCHDB-393 imply this might not be trivial.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.