Samuel Tardieu (JIRA | 27 Apr 17:36 2015
Picon

[jira] [Created] (COUCHDB-2676) DELETE of a database returns JSON answer with type text/plain

Samuel Tardieu created COUCHDB-2676:
---------------------------------------

             Summary: DELETE of a database returns JSON answer with type text/plain
                 Key: COUCHDB-2676
                 URL: https://issues.apache.org/jira/browse/COUCHDB-2676
             Project: CouchDB
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: HTTP Interface
            Reporter: Samuel Tardieu

DELETE should return its response with a "application/json" MIME type.

{code}
% curl -v -X DELETE http://localhost:5984/test 
*   Trying ::1...
* Connected to localhost (::1) port 5984 (#0)
> DELETE /test HTTP/1.1
> Host: localhost:5984
> User-Agent: curl/7.42.0
> Accept: */*
> 
< HTTP/1.1 200 OK
< Server: CouchDB/1.6.1 (Erlang OTP/17)
< Date: Mon, 27 Apr 2015 15:30:14 GMT
< Content-Type: text/plain; charset=utf-8
< Content-Length: 12
< Cache-Control: must-revalidate
< 
(Continue reading)

ILYA (JIRA | 27 Apr 16:54 2015
Picon

[jira] [Commented] (COUCHDB-2667) Regression: /_db_updates response format changed


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

ILYA commented on COUCHDB-2667:
-------------------------------

Should be fixed in https://github.com/apache/couchdb-global-changes/pull/5

> Regression: /_db_updates response format changed
> ------------------------------------------------
>
>                 Key: COUCHDB-2667
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2667
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: HTTP Interface
>            Reporter: Alexander Shorin
>            Assignee: ILYA
>            Priority: Blocker
>              Labels: regression
>             Fix For: 2.0.0
>
>
> In CouchDB 2.0:
> {code}
> {
>     "dbname": "aiocouchdb/1837f0420b9443f79b039b0aec01c7b2",
(Continue reading)

robertkowalski | 27 Apr 14:56 2015
Picon

[GitHub] couchdb pull request: add no-join option

GitHub user robertkowalski opened a pull request:

    https://github.com/apache/couchdb/pull/315

    add no-join option

    in order to make testing `/_setup_cluster` easier

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/robertkowalski/couchdb no-join

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb/pull/315.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 #315

----
commit c32a0acc6b1933aaddf4a38f0c221fd8f5f65dba
Author: Robert Kowalski <rok@...>
Date:   2015-04-27T12:48:38Z

    add no-join option

    in order to make testing `/_setup_cluster` easier

(Continue reading)

Picon

[jira] [Created] (COUCHDB-2675) lklk

ASF subversion and git services created COUCHDB-2675:
--------------------------------------------------------

             Summary: lklk
                 Key: COUCHDB-2675
                 URL: https://issues.apache.org/jira/browse/COUCHDB-2675
             Project: CouchDB
          Issue Type: Bug
      Security Level: public (Regular issues)
            Reporter: ASF subversion and git services

lklk

*Reporter*: edwesdfsdf
*E-mail*: [mailto:sdfsdf@...]

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Will Holley (JIRA | 26 Apr 20:35 2015
Picon

[jira] [Created] (COUCHDB-2674) Inconsistent handling of URL encoded design doc name between clustered and non-clustered interfaces

Will Holley created COUCHDB-2674:
------------------------------------

             Summary: Inconsistent handling of URL encoded design doc name between clustered and non-clustered interfaces
                 Key: COUCHDB-2674
                 URL: https://issues.apache.org/jira/browse/COUCHDB-2674
             Project: CouchDB
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: Database Core
            Reporter: Will Holley

In CouchDB 1.6 (and non-clustered 2.X), a request to GET a design document where the full design document
name is URL encoded results in a 301 redirect:

{code}
$ curl -v http://127.0.0.1:15986/test/_design%2Ffoo
> GET /test/_design%2Ffoo HTTP/1.1
> User-Agent: curl/7.37.1
> Host: 127.0.0.1:15986
> Accept: */*
> 
< HTTP/1.1 301 Moved Permanently
* Server CouchDB/44fe5b6 (Erlang OTP/17) is not blacklisted
< Server: CouchDB/44fe5b6 (Erlang OTP/17)
< Location: http://127.0.0.1:15986/test/_design/foo
< Date: Sun, 26 Apr 2015 18:18:30 GMT
< Content-Length: 0
< 
* Connection #0 to host 127.0.0.1 left intact
(Continue reading)

ASF GitHub Bot (JIRA | 26 Apr 00:46 2015
Picon

[jira] [Commented] (COUCHDB-2673) "Location" header in HTTP response should properly encode the document _id


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

ASF GitHub Bot commented on COUCHDB-2673:
-----------------------------------------

GitHub user samueltardieu opened a pull request:

    https://github.com/apache/couchdb/pull/314

    Properly escape Location: HTTP header

    Non-ASCII characters in the "Location:" header must be URL-encoded. This
    can happen if a document is inserted with a user-defined "_id"
    containing non-ASCII characters or if a filename contains non-ASCII
    characters.

    Fixes COUCHDB-2673

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/samueltardieu/couchdb urlencode-location-header

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb/pull/314.patch

To close this pull request, make a commit to your master/trunk branch
(Continue reading)

samueltardieu | 26 Apr 00:46 2015
Picon

[GitHub] couchdb pull request: Properly escape Location: HTTP header

GitHub user samueltardieu opened a pull request:

    https://github.com/apache/couchdb/pull/314

    Properly escape Location: HTTP header

    Non-ASCII characters in the "Location:" header must be URL-encoded. This
    can happen if a document is inserted with a user-defined "_id"
    containing non-ASCII characters or if a filename contains non-ASCII
    characters.

    Fixes COUCHDB-2673

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/samueltardieu/couchdb urlencode-location-header

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb/pull/314.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 #314

----
commit a3fee552ddc6014767f1ed393f0960ca1ada3fe5
Author: Samuel Tardieu <sam@...>
Date:   2015-04-25T22:10:04Z
(Continue reading)

Samuel Tardieu (JIRA | 25 Apr 23:55 2015
Picon

[jira] [Created] (COUCHDB-2673) "Location" header in HTTP response should properly encode the document _id

Samuel Tardieu created COUCHDB-2673:
---------------------------------------

             Summary: "Location" header in HTTP response should properly encode the document _id
                 Key: COUCHDB-2673
                 URL: https://issues.apache.org/jira/browse/COUCHDB-2673
             Project: CouchDB
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: Database Core
            Reporter: Samuel Tardieu

When inserting a document in a CouchDB 1.6.1 database, the response sent by CouchDB contains a "Location"
HTTP header with the URI of the newly created document.

However, if the "_id" of the new document contains non-ASCII characters, this "Location" header is not
properly encoded.

Example:

{code}
 % curl -v -H "Content-Type: application/json" -X POST http://localhost:5984/test/ --data '{"_id": "xxxé"}'
*   Trying ::1...
* Connected to localhost (::1) port 5984 (#0)
> POST /test/ HTTP/1.1
> Host: localhost:5984
> User-Agent: curl/7.42.0
> Accept: */*
> Content-Type: application/json
> Content-Length: 16
(Continue reading)

Picon

[jira] [Commented] (COUCHDB-1787) Automate release process documentation


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

Amarnath Beedimane Hanumantharaya commented on COUCHDB-1787:
------------------------------------------------------------

Hi Robert,
still now i didn't get confirmation of my proposal?

> Automate release process documentation
> --------------------------------------
>
>                 Key: COUCHDB-1787
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1787
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Build System, Documentation
>            Reporter: Dave Cottlehuber
>              Labels: gsoc, gsoc2015, mentor
>
> The release process today contains a large number of manual transformation steps.
> Fixing this will make the release process significantly easier for release managers, as well as less error-prone.
> Ideally the output formats (NEWS, CHANGES in source tree, and HTML snippets for http://couchdb.org/
website and http://blogs.apache.org/couchdb ) can be auto-generated from either the .rst files in
share/doc/src using sphinx's .versionaddded/changed tags, or potentially from commit messages if
this is appropriate.
> CouchDB documentation is generated today from restructured text using python code, and rolled into the
release documentation during `make distcheck`.
(Continue reading)

benkeen | 24 Apr 19:22 2015
Picon

[GitHub] couchdb-fauxton pull request: Fix for right panel not being scroll...

GitHub user benkeen opened a pull request:

    https://github.com/apache/couchdb-fauxton/pull/394

    Fix for right panel not being scrollable

    Certain two-panel pages like the Create Admin page had overflow
    hidden so content would get cut off an unreachable for smaller
    browser widths. This patches it to only apply the overflow for pages
    that need it (e.g. the doc list).

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/benkeen/couchdb-fauxton two-panel-scrollable-fix

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb-fauxton/pull/394.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 #394

----
commit 7050442c3034af8068b5fa104e9ff65690d72ecb
Author: Ben Keen <ben.keen@...>
Date:   2015-04-24T17:20:19Z

    Fix for right panel not being scrollable
(Continue reading)

Alexander Shorin (JIRA | 23 Apr 22:45 2015
Picon

[jira] [Resolved] (COUCHDB-2656) Update couch_mrview to use chttpd provided functions


     [
https://issues.apache.org/jira/browse/COUCHDB-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Shorin resolved COUCHDB-2656.
---------------------------------------
    Resolution: Fixed

All merged. Thank you!

> Update couch_mrview to use chttpd provided functions
> ----------------------------------------------------
>
>                 Key: COUCHDB-2656
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2656
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Database Core
>            Reporter: ILYA
>            Assignee: ILYA
>
> couch_mrview uses functions from couch_http. For example send_external_response is used by
couch_mrview_show. This brakes CORS support. Since couch_httpd's version of send_external_response
doesn't have support for CORS compared to chttpd's version https://github.com/apache/couchdb-chttpd/blob/master/src/chttpd_external.erl#L127.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

(Continue reading)


Gmane