[
https://issues.apache.org/jira/browse/COUCHDB-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Joseph Davis updated COUCHDB-735:
--------------------------------------
Skill Level: Regular Contributors Level (Easy to Medium)
> Support HTTP POST for the change notification filter API
> --------------------------------------------------------
>
> Key: COUCHDB-735
> URL: https://issues.apache.org/jira/browse/COUCHDB-735
> Project: CouchDB
> Issue Type: Improvement
> Components: HTTP Interface
> Affects Versions: 0.11
> Reporter: Ning Tan
> Attachments: changes_filter_with_post.patch
>
>
> Currently the change notification filters only support HTTP GET. This limits
> their usefulness for cases where the filter criteria passed in exceed URL
> query length limitations. If the API supports HTTP POST, the filter function
> can then inspect the BODY of the request for filtering criteria.
> I started a discussion on the mailing list here:
> http://mail-archives.apache.org/mod_mbox/couchdb-user/201004.mbox/browser.
> Chris suggested that I modify the change API to support POST (in the Erlang
> code) myself as an experiment. I was able to verify that the filter function
> was able to see the BODY of the request. However, the changes feed (with the
> filtering function) hangs whenever there is a BODY in the request (for both
> GET and POST verbs).
> I'm attaching a patch that contains the change Chris proposed as well as the
> updated Futon JavaScript test file for the changes API. The test currently
> times out (and fails). It should work once the feature is implemented.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
