Update: The real issue is that flash-player tries to load any asset as a video from the address http://www.arsnavigandi-m%FCnchen.de insted of the IDN-encoded URL.
This is a mass search for bugs which are in the Firefox General component, are UNCO, have not been changed for 500 days and have an unspecified version. Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Bug still exists
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:10.0) Gecko/20100101 Firefox/10.0
Confirmed for: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20100101 Firefox/12.0 Another example: http://www.bäume-für-deutschland.de/ location.host is "www.bäume-für-deutschland.de" instead of "www.xn--bume-fr-deutschland-gwb32c.de". Flashplayer fails to load clips from this domain.
Confirmed for: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20100101 Firefox/17.0 example: http://gästehaus-kapellen-drusweiler.de/ window.location.host: gästehaus-kapellen-drusweiler.de clip loaded in flash reports url: http://gÃ¤stehaus-kapellen-drusweiler.de/path-to-swf/container.swf The mistake in the URL is true. It appears that the a-umlaut is incorrectly encoded; perhaps the host name should be in punycode.
This is still an issue. We discovered this due to the newly introduced usage of window.location.host in Moodle. See https://tracker.moodle.org/browse/MDL-57092.
The problem with punycode still exists! Some WordPress plugins wont run on our site (https://bluetooth-kopfhörer-test.com/) because of this issue... One example is the plugin "heatmap", which wont work with Firefox but works perfeclty fine with other browsers. Can anyone tell when the bug will be fixed? I see that this was mentioned 9 years (!) ago for the first time.