You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2010/03/05 02:55:55 UTC

[jira] Updated: (MRM-1351) Verification of a deployed artifact

     [ http://jira.codehaus.org/browse/MRM-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MRM-1351:
------------------------------

    Fix Version/s: Backlog

Placing in the backlog for now, but we'll certainly consider this for 1.4 depending on how it progresses.

> Verification of a deployed artifact 
> ------------------------------------
>
>                 Key: MRM-1351
>                 URL: http://jira.codehaus.org/browse/MRM-1351
>             Project: Archiva
>          Issue Type: Improvement
>    Affects Versions: 1.3
>            Reporter: Marc Lustig
>            Priority: Critical
>             Fix For: Backlog
>
>
> Currently, Archiva verifies a deployed artifact only by comparing the content-length HTTP header with the actual file-size of the uploaded file.
> To better prevent corrupt artifacts, it would help to verify the integrity of the artifact by comparing its local hashcode (sha1 or md5) with the one that has just been generated in Archiva.
> In case the hashes differ, 
> a) an HTTP 400 status should be returned
> b) an error should be logged.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira