3 Replies Latest reply on Nov 25, 2009 12:17 PM by OrangeHaze

    Using Modules and Flex Framework RSLs over HTTPS

    OrangeHaze

      Hello,

       

      I wanted to know if someone can verify a few things for me.

       

      There is currently a bug in the flex that causes modules loaded simultaneously to sometimes fail to load if they are using the flex framework RSLs.

       

      SWFs don't cache over HTTPs, so if a .swz fails to load and get cached in the flash player, then every time my main location loads a new module it has to download the framework.swf again.

       

      The problem i'm running into, is that the first time my application loads over https, it looks for the framework.swf (omitted build #) at http://framework.swf, instead of http://www.mydomain.com/framework.swf, eventually it somehow finds the right location. But I believe its buggy behavior.

       

      Any insight would be greatly appreciated.

        • 1. Re: Using Modules and Flex Framework RSLs over HTTPS
          Darrell Loverin Level 4

          >>There is currently a bug in the flex that causes modules loaded simultaneously to sometimes fail to load if they are using the flex framework RSLs.

          Is there a bug for this issue?

           

          >>SWFs don't cache over HTTPs, so if a .swz fails to load and get cached in the flash player, then every time my main location loads a new module it has to download the framework.swf again.

          Are you seeing an error message in the debug player telling you why the .swz is failing to load?

           

          Modules shouldn't need to load the framework RSL. Have the main application load the framework RSL and all the module can inherit the classes. You can then make your modules smaller by compiling them with framework.swc on the external library path.

           

           

          >>The problem i'm running into, is that the first time my application loads over https, it looks for the framework.swf (omitted build #) at http://framework.swf, instead of http://www.mydomain.com/framework.swf, eventually it somehow finds the right location. But I believe its buggy behavior.

          Is there a bug for this issue?

           

           

          -Darrell

          • 2. Re: Using Modules and Flex Framework RSLs over HTTPS
            LeoBent

            Hi

             

            I am running into a similar problem.

             

            I have a build script with the following properties

             

            <property name="rsl.url" value="/DTCF/bfp/rsl"/>

            <property name="flex-version" value="3.3"/>

            <property name="flex-build-number" value="${flex-version}.0.4852"/>

             

            Within the mxmlc task it has this.

             

            <runtime-shared-library-path  path-element="${flex-lib.dir}/framework.swc">
                        <url rsl-url="${rsl.url}/framework_${flex-build-number}.swz"/>
                        <url rsl-url="${rsl.url}/framework_${flex-build-number}.swf"/>

            </runtime-shared-library-path>
            <runtime-shared-library-path path-element="${flex-lib.dir}/rpc.swc">
                        <url rsl-url="${rsl.url}/rpc_${flex-build-number}.swz"/>
                        <url rsl-url="${rsl.url}/rpc_${flex-build-number}.swf"/>

            </runtime-shared-library-path>

             

             

            Now when i have deployed the application and access it, I am getting this in the HttpFox firefox addon.

            00:00:07.756    2.597    411    0    GET    (Error)    NS_ERROR_UNKNOWN_HOST    http://dtcf/bfp/rsl/framework_3.3.0.4852.swf

            00:00:07.956    2.398    405    0    GET    (Error)    NS_ERROR_UNKNOWN_HOST    http://dtcf/bfp/rsl/rpc_3.3.0.4852.swf

             


            It seems like the relative path defined in the build script is not working.

            But still the application runs ok, but looks like the caching stuff is not working.

             

            This is however working fine for an application that was built against flex 3.0.

             

            Stuff that we have tried:

             

            • Adding the static-rsls=false param to the mxmlc task  - Did not fix the problem
            • Changing the relative path to an absolute path  - Did work , but is not a suitable fix.
            • 3. Re: Using Modules and Flex Framework RSLs over HTTPS
              OrangeHaze Level 1

              It turns out my problem appears to be the MIME type is not set on the server for .swz files. Once this is fixed I'll post back to if it was the solution or not.