flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Mclean (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-34425) Make MD5 change non fatal
Date Mon, 27 Oct 2014 01:29:34 GMT

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

Justin Mclean commented on FLEX-34425:

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
> 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

View raw message