You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "Justin Mclean (JIRA)" <ji...@apache.org> on 2014/10/27 05:21:34 UTC

[jira] [Comment Edited] (FLEX-34425) Make MD5 change non fatal

    [ https://issues.apache.org/jira/browse/FLEX-34425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184735#comment-14184735 ] 

Justin Mclean edited comment on FLEX-34425 at 10/27/14 4:20 AM:
----------------------------------------------------------------

There are two main reasons (ignoring caching) the MD5 could could fail:
- The file downloaded is corrupt
- The MD5 was not obtained correctly from the dist area.

Currently the code does't check that the MD5 is valid, we should check for this and continue if we don't have a valid MD5.


was (Author: jmclean):
There are two main reasons (ignoring caching) the MD5 chaco could fail:
- The file downloaded is corrupt
- The MD5 was not obtained correct from the dist area.

Currently the code does't check that the MD5 is valid, we should check for this and continue if we don't have a valid MD5.

> Make MD5 change non fatal
> -------------------------
>
>                 Key: FLEX-34425
>                 URL: https://issues.apache.org/jira/browse/FLEX-34425
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: InstallApacheFlex, Installer
>    Affects Versions: Install Apache Flex 3.1
>            Reporter: Justin Mclean
>            Assignee: Justin Mclean
>
> If the MD5 changes for player global swc (or other download component) the installer fails to complete and will continue to do so for all user until the MD5 hash is updated. Would be better to warn user there is a difference explain the two possible reasons (i.e. bad download now possible cached in your browser cache or newer version of software available) and ask to continue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)