couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filipe Manana (JIRA)" <>
Subject [jira] Updated: (COUCHDB-558) Validate Content-MD5 request headers on uploads
Date Fri, 27 Nov 2009 21:21:20 GMT


Filipe Manana updated COUCHDB-558:

    Attachment: jira-couchdb-558-10th-try-trunk.patch

Nothing new in this new patch.

Only modification is the use of couch_util:decode_json/1 instead of mochijson2:decode/1 in
the test case.

Just did a git svn rebase today and got the surprise that ?JSON_DECODE is now a shortcut for
the new couch_util:decode_json/1 and no longer a shortcut to mochijson2:decode/1, which returns
a slightly different shapped tuple. This was causing the test case to fail.


> Validate Content-MD5 request headers on uploads
> -----------------------------------------------
>                 Key: COUCHDB-558
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Database Core, HTTP Interface
>            Reporter: Adam Kocoloski
>             Fix For: 0.11
>         Attachments: jira-couchdb-558-10th-try-trunk.patch, jira-couchdb-558-4th-try.patch,
jira-couchdb-558-5th-try.patch, jira-couchdb-558-6th-try-trunk.patch, jira-couchdb-558-7th-try-trunk.patch,
jira-couchdb-558-8th-try-trunk.patch, jira-couchdb-558-9th-try-trunk.patch, jira-couchdb-558-for-trunk-2nd-try.patch,
jira-couchdb-558-for-trunk-3rd-try.patch, jira-couchdb-558-for-trunk.patch, run.tpl.patch
> We could detect in-flight data corruption if a client sends a Content-MD5 header along
with the data and Couch validates the MD5 on arrival.
> RFC1864 - The Content-MD5 Header Field

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message