You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by kxepal <gi...@git.apache.org> on 2015/10/21 11:37:02 UTC
[GitHub] couchdb-chttpd pull request: Escape database name on POST /_replic...
GitHub user kxepal opened a pull request:
https://github.com/apache/couchdb-chttpd/pull/84
Escape database name on POST /_replicate
COUCHDB-2666
Reintroduce https://github.com/apache/couchdb-chttpd/pull/35 changes since issue was not fixed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kxepal/couchdb-chttpd 2666-replicate-db-escape
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-chttpd/pull/84.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #84
----
commit bf604a5ea092d3b90ba4fed8483c000d68d0130f
Author: Alexander Shorin <kx...@apache.org>
Date: 2015-10-20T18:04:31Z
Use real chttpd port for URI construct
Those port that we get from config works fine until we start to ask
for a random port.
commit 976b09a8b44a2bcc082450a48962f95ebd6c0b0d
Author: Alexander Shorin <kx...@apache.org>
Date: 2015-10-20T18:13:39Z
Escape database name on POST /_replicate
COUCHDB-2666
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-chttpd pull request: Escape database name on POST /_replic...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/couchdb-chttpd/pull/84
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---