couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcos Zanona (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1101) Headers from update handler not returned when a document is created/modified
Date Mon, 04 Jul 2011 19:43:21 GMT

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

Marcos Zanona commented on COUCHDB-1101:
----------------------------------------

As far as I can see Jonathan already posted a solution on February https://issues.apache.org/jira/browse/COUCHDB-648?focusedCommentId=12990936&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12990936
.

I performed the test and it not only added the possibility to add the status code to the response
as it maintain the whole header as it was supposed to be.

Please consider adding this to the trunk.

> Headers from update handler not returned when a document is created/modified
> ----------------------------------------------------------------------------
>
>                 Key: COUCHDB-1101
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1101
>             Project: CouchDB
>          Issue Type: Bug
>          Components: HTTP Interface
>    Affects Versions: 1.0.2
>         Environment: Fedora 14, 4 Cores, 4 GB RAM
>            Reporter: Jiri Sedlacek
>            Priority: Minor
>
> I expect from this update handler to return "X-my-header" header in response. It does
not.
> function(doc,req) { 
>   var resp = { "headers" : {  "X-my-header": "application" } , "body": "" }; 
>   return [{_id:req.uuid}, resp];
> }
> Changing the return to:
>   return [null, resp];
> helps.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message