[FLEX-27551] Not able to replace an expired RSL in the Flash Player cache

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: Adobe Flex SDK Previous
• Component/s: Runtime Shared Libraries
• Environment: Affected OS(s): Windows; Affected OS(s): Windows XP; Language Found: English
• Assignee: Unassigned
• Reporter: Adobe JIRA
• Created: 18/May/11 12:07
• Updated: 12/Oct/11 11:17

Description

Steps to reproduce:
1.a. Compile this application with both the 4.5 beta sdk (4.5.0.17689) and the 4.5 Release SDK (4.5.0.20967). Or use the pre-built applications, http://blogs.adobe.com/dloverin/files/2011/05/VideoTestBeta.swf (4.5.0.17689) and http://blogs.adobe.com/dloverin/files/2011/05/VideoTest.swf (4.5.0.20967).

<?xml version="1.0" encoding="utf-8"?>
<!-- Simple example to demonstrate the Spark VideoDisplay control. -->
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx">

<s:Panel title="Halo VideoDisplay Control Example"
width="75%" height="75%"
horizontalCenter="0" verticalCenter="0">
<s:VGroup left="10" right="10" top="10" bottom="10" horizontalAlign="center">
<s:VideoPlayer source="Small.flv" autoPlay="false"/>
</s:VGroup>
</s:Panel>

</s:Application>

2. Run the beta version of the application (http://blogs.adobe.com/dloverin/files/2011/05/VideoTestBeta.swf). The application loads successfully and populates the Flash Player cache.
3. Change the system date to five year ahead.
4. Run the beta version of the application again. Should receive "Error 2046: The loaded file did not have a valid signature." It seems the beta RSLs where signed with a five year certificate.
5. Run the released version of the application.

Actual Results:
The application built with the release version of the Flex SDK fails with the same error. The only way to load the release version of the application is to clear the Flash Player cache.

Expected Results:
The Flash Player treats the certificate expiration as a cache miss, read the RSL in the URLRequest.url, and remove the RSL from the cache. This would allow an invalid certificate to be replaced in the cache by the application.

Workaround (if any):
Clear the Flash Player cache before loading the release version of the application. I don't think that developers of Flex Applications will find it acceptable that they need to tell their users to clear their Flash Player cache in order to continue to use their application.