We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Mozilla 도움말 검색

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

자세히 살펴보기

Mp3 file plays by URL, but fails to play in audio tag.

  • 3 답장
  • 3 이 문제를 만남
  • 1 보기
  • 최종 답변자: soumyadipDe

more options

This URL, when hit directly, it plays.

http://ezto-cf-media.mheducation.com/Media/Connect_Production/Externalized/Audio/13252700146307755.mp3

But when embedded in audio tag, it fails to play and firefox shows "Media resource http://ezto-cf-media.mheducation.com/Media/Connect_Production/Externalized/Audio/13252700146307755.mp3 could not be decoded. All candidate resources failed to load. Media load paused."

Audio tag is implemented as,

<audio class="audio-player" controls><source type="audio/mpeg" src="http://ezto-cf-media.mheducation.com/Media/Connect_Production/Externalized/Audio/13252700146307755.mp3"></source></audio>
This URL, when hit directly, it plays. http://ezto-cf-media.mheducation.com/Media/Connect_Production/Externalized/Audio/13252700146307755.mp3 But when embedded in audio tag, it fails to play and firefox shows "Media resource http://ezto-cf-media.mheducation.com/Media/Connect_Production/Externalized/Audio/13252700146307755.mp3 could not be decoded. All candidate resources failed to load. Media load paused." Audio tag is implemented as, <pre><nowiki><audio class="audio-player" controls><source type="audio/mpeg" src="http://ezto-cf-media.mheducation.com/Media/Connect_Production/Externalized/Audio/13252700146307755.mp3"></source></audio></nowiki></pre>

글쓴이 cor-el 수정일시

모든 댓글 (3)

more options

HTML is used as below.

<audio class="audio-player" controls> <source type="audio/mpeg" src="http://ezto-cf-media.mheducation.com/Media/Connect_Production/Externalized/Audio/13252700146307755.mp3"></source></audio>

글쓴이 cor-el 수정일시

more options

I'm not sure what kind of file this is because the Network Monitor shows it as type audio/x-wav when used with the audio tag. When the URL is loaded via the location bar then the Network Monitor shows audio/mpeg. The decoder used with the audio tag might not recognize the file correctly.

more options

The "Content-type" in response header shows "audio/mpeg". Can you please let me know where you are seeing "audio/x-wav". Attaching screenshot.

Thanks