Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Flash plugin can't load xml files from the unicode url

  • 11 답장
  • 2 이 문제를 만남
  • 7 보기
  • 최종 답변자: januzi

more options

Hello

So, there's a problem with the unicode urls. For some reason Firefox passes wrong url to the flash plugin, so it can't load xml files. The url of the website is in the unicode and according to the Firebug everything on the website is loading with the "xn--" in the url, except for the xml file, which has got %'s. There's no problem with the other web browsers, so I assume that this has something to do with the Firefox itself. So, is there something that I can do with the flash file (or rather with the person that made this flash file) to be able to load xml files?

Edit: Direct access to swf file works fine. The xml config gets loaded without any problems. Looks like that <object> is somehow broken.

Hello So, there's a problem with the unicode urls. For some reason Firefox passes wrong url to the flash plugin, so it can't load xml files. The url of the website is in the unicode and according to the Firebug everything on the website is loading with the "xn--" in the url, except for the xml file, which has got %'s. There's no problem with the other web browsers, so I assume that this has something to do with the Firefox itself. So, is there something that I can do with the flash file (or rather with the person that made this flash file) to be able to load xml files? Edit: Direct access to swf file works fine. The xml config gets loaded without any problems. Looks like that <object> is somehow broken.

글쓴이 januzi 수정일시

모든 댓글 (11)

more options

Please make sure your flash plugin is up to date and your Firefox browser is up to date.

more options

Both, plugin and Firefox, are up to date.

more options

The System Details List shows that you have multiple Flash plugins.

  • Shockwave Flash 20.0 r0
  • Shockwave Flash 21.0 r0

You can find the installation path of all plugins on the about:plugins page.

You can check the Flash player installation folder for multiple Flash player plugins and remove older version(s) of the plugin (NPSWF32) and possibly (re)install the latest Flash player.

  • (32 bit Windows) C:\Windows\System32\Macromed\Flash\
  • (64 bit Windows) C:\Windows\SysWOW64\Macromed\Flash\
more options

Nope. After removing dll and restarting Firefox flash animation still can't load xml file.

more options

Do you have a testcase to provide to reproduce the issue with FF45?

more options

Sure. Webpage: http://mediatorzysądowi.pl/sad.html and direct access to the swf: http://mediatorzysądowi.pl/sad.swf

more options

januzi said

Sure. Webpage: http://mediatorzysądowi.pl/sad.html and direct access to the swf: http://mediatorzysądowi.pl/sad.swf

Thanks. I tried with various old versions of Firefox (back to FF12) and Flash 21.0.0.182, all have the same issue (xml file not loading).

Did it use to work with previous versions of Flash, like 20 or 19? If yes, maybe there is an issue with Flash 21.

more options

Oxylatium said

Did it use to work with previous versions of Flash, like 20 or 19? If yes, maybe there is an issue with Flash 21.

Last time somebody wanted similar flash file to work on the unicode domain was more than one year ago. It was version 16 or 17 and it wasn't working on it either.

One thing that bothers me is that, how come swf file executed directly has got no problems what so ever? Isn't the embed code for the <object> the same as for direct access?

I've also found this bugs: https://bugzilla.mozilla.org/show_bug.cgi?id=1142083 and https://bugzilla.mozilla.org/show_bug.cgi?id=1228639 . If I understand this correctly, Firefox 45 should fix unicode domain error? Or this fix is working only with the urls and not with the environment variables inside plugin-container?

글쓴이 januzi 수정일시

more options

Your testcase doesn't work in old versions of Firefox, I doubt there is a regression in FF45.

more options

Create a new profile to test if your current profile is causing the problem.

See "Creating a profile":

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.

more options

cor-el said

Create a new profile to test if your current profile is causing the problem.

I believe that Oxylatium's profile is good enough for this test. So, there's nothing wrong with the profiles.