New issue
Advanced search Search tips

Issue 594139 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

createMediaElementSource throws Cross-Origin error when source stream is set using IP but it works if you use a host name.

Reported by mwork...@gmail.com, Mar 11 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36

Example URL:

Steps to reproduce the problem:
If the audio stream source is set using IP and even if the crossOrigin property is set to anonymous, the Cross-Origin error is thrown and audio input goes silent when the source is connected to the audio analyser. The same process works fine when you use a full host name instead of IP address.

I'm setting the stream source like this,        audio.setAttribute('src', url);

What is the expected behavior?
Should have been able to extract frequencyBinCount from the the audio analyser

What went wrong?
No sound, and get this error,

MediaElementAudioSource outputs zeroes due to CORS access restrictions for http://80.252.100.142:8000/stream

Did this work before? N/A 

Is it a problem with Flash or HTML5? N/A

Does this work in other browsers? N/A 

Chrome version: 48.0.2564.116  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 21.0 r0
 
Components: -Internals>Media Internals>Media>Source
Owner: wolenetz@chromium.org
Status: Assigned (was: Unconfirmed)
matt, can you take a look?
Cc: wolenetz@chromium.org
Labels: MSEscrubbed
Owner: chcunningham@chromium.org
Chris, can you take a look please?
Trying to setup no help sorry sir will do better

country.pullins0@gmail.com

createMediaElementSource throws Cross-Origin error when source stream is
set using IP but it works if you use a host name.
Labels: StaleAssigned
This bug has been stale for > 1 year. If you still want to keep it, please change StaleAssigned label to StaleKeep. If you don't want to keep it anymore, you don't need do anything, I will close it in 30 days.
thanks

Labels: StaleClosed
Status: WontFix (was: Assigned)
this bug has been stale for > 1 year. resolve as won't fix with label StaleClosed. If you think it's worth to keep, please re-activate and assign appropriately.
mworkuww@gmail.com - sorry for the delay. 

I've just tested my local machine using setAttribute and a ip source of 127.0.0.1/... - no issues. https://jsfiddle.net/oen0eLfw/

If you still observe this issue please link to a demo and I'll dig in. 


Sign in to add a comment