[ https://issues.apache.org/jira/browse/COUCHDB-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Davies updated COUCHDB-441: --------------------------------- Attachment: COUCHDB-441.2.patch Updated patch that uses req.userCtx now that OAuth/cookie auth has landed. > Finally implement pre-write-doc-edit handlers. > ---------------------------------------------- > > Key: COUCHDB-441 > URL: https://issues.apache.org/jira/browse/COUCHDB-441 > Project: CouchDB > Issue Type: Improvement > Components: HTTP Interface > Affects Versions: 0.10 > Reporter: Curt Arnold > Fix For: 0.10 > > Attachments: COUCHDB-441.2.patch, COUCHDB-441.patch > > > It would be useful for auditing to have the identity of the user who inserted > a new revision and the timestamp of the operation to be inserted in the > document in the same way that the new revision number is. > Doing this at the application level is not adequate since it would be readily > spoofable and would bypass the authentication handler. > There is a comment in couch_db:update_docs about generating new revision ids, > but I couldn't quite comprehend what specific code was responsible for > inserting the id into the document. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.