At my blogspot, I posted my javascript workaround for uploads in firefox
over SSL.

Please see http://sethonflex.blogspot.com/

 

I don't have Adobe Share access, but I would love to see how they accomplish
fileupload in firefox over SSL - I don't think they can do it without using
filereference.upload unless you click something granting the application
special access. (because filereference is the only way into the user files
when you're within the sandbox,  I believe).

 

In any case, I hope my workaround might help some of you until Adobe fixes
their flash player!

 

Seth

 

From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Richard Rodseth
Sent: Friday, October 26, 2007 10:45 AM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] FW: FileReference.upload()

 

I've received confirmation from Dave Wolf at Cynergy that this is a
long-standing problem.

I notice that Adobe Share uploads work in Firefox. It would appear
that they might be using AMF. Any idea how that might work? I don't
believe there's a way to get to file bytes from a FileReference
(presumably a security concern).

At this point I'm looking for workarounds that don't involve too much
in the way of UI compromise.

On 10/25/07, Richard Rodseth <[EMAIL PROTECTED]
<mailto:rrodseth%40gmail.com> > wrote:
> What, no votes yet? :)
>
> Here's the link:
>
> http://bugs.adobe.com/jira/browse/SDK-13196
>
> On 10/25/07, Richard Rodseth <[EMAIL PROTECTED]
<mailto:rrodseth%40gmail.com> > wrote:
> > Not sure what the fixed bug is that Matt refers to, but I just logged
> >
> > SDK-13196
> >
> > Please cast your votes and/or add your experience reports.
> >
> > - Richard
> >
> > On 7/23/07, Matt Chotin <[EMAIL PROTECTED] <mailto:mchotin%40adobe.com>
> wrote:
> > >
> > > How is your crossdomain file set up? I see one bug for HTTPS upload
that
> > > was not reproducible and another that we fixed recently when a default
> > > crossdomain file didn't seem to work (fix should be available in a
nightly
> > > build of the SDK).
> > >
> > >
> > >
> > > Matt
> > >
> >
>

 

Reply via email to