[FLEX-27436] A policy file is loaded when reading a SWZ file that is already cached

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: Adobe Flex SDK 4.5 (Release)
• Component/s: Runtime Shared Libraries
• Environment: Affected OS(s): Windows; Affected OS(s): Windows XP; Language Found: English
• Assignee: Unassigned
• Reporter: Adobe JIRA
• Created: 04/May/11 10:52
• Updated: 25/May/11 10:30

Description

Steps to reproduce:
1. Build a simple "Hello World" application.
<?xml version="1.0" encoding="utf-8"?>
<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" minWidth="955" minHeight="600">
<fx:Declarations>
<!-- Place non-visual elements (e.g., services, value objects) here -->
</fx:Declarations>
<s:Label text="Hello World" />
</s:Application>

2. If compiling in Flex Builder, deselect the checkbox titled "Use local debug runtime shared libraries when debugging" on the "Flex Build Path" properties page, "Library Path" tab.
3. Clear the Flash Player cache.
4. Run the application. Notice the warning:
Warning: Ignoring 'secure' attribute in policy file from http://fpdownload.adobe.com/pub/swz/crossdomain.xml. The 'secure' attribute is only permitted in HTTPS and socket policy files. See http://www.adobe.com/go/strict_policy_files for details.

This is caused by reading the policy file. This should happen the first time and is ok.

5. Run the application a second time.

Actual Results:
The same policy file warning is displayed again even when all the RSLs are loaded from the cache. This implies the policy file is read again. I verified that it is read again using Charles.

Expected Results:
The policy file should not be read. In my test, reading the policy file and the master policy consumed 516 ms. The two files totaled 2.21 KB. This information was obtained from Charles.

Workaround (if any):