Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Playing mp3 Shoutcast streams with HTML5 audio in Firefox?

  • 1 Antwort
  • 21 haben dieses Problem
  • 1 Aufruf
  • Letzte Antwort von biggyspender

more options

I'm trying to play mp3 shoutcast stream radio stations with HTML5 audio.

I don't think it will be relevant but here is the code anyway:

var player = new Audio(); player.autobuffer = true; player.src = "http://173.192.48.71:9048/;"; player.volume = 1; player.play();

Shoutcast detects that request comes from browser and returns radio status page, so I put ";" at the end of stream which forces server to return audio stream instead of status page. This works fine in Chrome and Safari, but not in Firefox.

Firefox for some reason detects this as text/plain content and refuses to play it with this error:

HTTP "Content-Type" of "text/plain" is not supported. Load of media resource http://173.192.48.71:9048/; failed.

But work in firefox 19. Oh God, what am I gonna do?

I'm trying to play mp3 shoutcast stream radio stations with HTML5 audio. I don't think it will be relevant but here is the code anyway: var player = new Audio(); player.autobuffer = true; player.src = "http://173.192.48.71:9048/;"; player.volume = 1; player.play(); Shoutcast detects that request comes from browser and returns radio status page, so I put ";" at the end of stream which forces server to return audio stream instead of status page. This works fine in Chrome and Safari, but not in Firefox. Firefox for some reason detects this as text/plain content and refuses to play it with this error: HTTP "Content-Type" of "text/plain" is not supported. Load of media resource http://173.192.48.71:9048/; failed. But work in firefox 19. Oh God, what am I gonna do?

Alle Antworten (1)

more options

So I downloaded the Mozilla code and fixed this issue. It looks like it will find its way into mozilla24.

Geändert am von biggyspender