[
https://issues.apache.org/jira/browse/COUCHDB-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zachary Zolton updated COUCHDB-190:
-----------------------------------
Attachment: COUCH-190.diff
Patch to fix COUCH-190:
* Changed /_uuids action to GET instead of POST
* Added broadly-compatible cache-busting headers to response
* Added to unit tests to JavaScript suite
> _uuid should respond to GET, not POST
> -------------------------------------
>
> Key: COUCHDB-190
> URL: https://issues.apache.org/jira/browse/COUCHDB-190
> Project: CouchDB
> Issue Type: Improvement
> Components: Database Core
> Affects Versions: 0.9
> Reporter: Matt Goodall
> Priority: Blocker
> Fix For: 0.9
>
> Attachments: COUCH-190.diff
>
>
> The /_uuid resource can happily return a response to a GET without being
> unresty. In fact, supporting POST is probably incorrect as it implies it
> would change server state.
> Quick summary:
> * _uuid never changes server state
> * calling _uuid multiple times does not impact other clients
> * that the resource returns something different each time it is requested
> does not mean it cannot be a POST
> * GET with proper cache control (i.e. don't cache it ever) will work equally
> well
> Full discussion can be found on the user m.l.,
> http://mail-archives.apache.org/mod_mbox/couchdb-user/200901.mbox/%3c21939021.1440421230910477169.javamail.serv...@perfora%3e.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
