FORUMS
Remove All Ads from XDA

CDN-FastServer streams are not working on firestick with mx player

6,707 posts
Thanks Meter: 3,549
 
By TheFixItMan, Senior Member on 30th May 2018, 04:20 PM
Post Reply Email Thread
5th June 2018, 01:41 PM |#11  
Recognized Contributor
Thanks Meter: 4,107
 
More
Quote:
Originally Posted by TheFixItMan

Yes Iv changed it & it made no difference
Apart from the Android version & the build name they both use mozilla 5.0
I changed it to the generic string but it made no difference


Guess I'll just to use vlc for these streams

Can you collect the network data using a debugging proxy? It will help us to understand better.
 
 
5th June 2018, 02:33 PM |#12  
TheFixItMan's Avatar
OP Senior Member
Flag London
Thanks Meter: 3,549
 
More
Quote:
Originally Posted by Thirumalai.K

Can you collect the network data using a debugging proxy? It will help us to understand better.

Not sure if this exactly what you wanted as I can only use apps which I find (no pc)

Iv captured the packets whilst playing the stream in mx player & vlc
You can see that vlc redirects to a different server where as mx player fails to redirect & says file not found
Attached Files
File Type: zip packet_captures.zip - [Click for QR Code] (8.39 MB, 8 views)
5th June 2018, 03:43 PM |#13  
Recognized Contributor
Thanks Meter: 4,107
 
More
Quote:
Originally Posted by TheFixItMan

Not sure if this exactly what you wanted as I can only use apps which I find (no pc)

Iv captured the packets whilst playing the stream in mx player & vlc
You can see that vlc redirects to a different server where as mx player fails to redirect & says file not found

Thanks for your efforts.
In fact, MX has tried the redirected URL. It looks like a server side restriction as we have expected.

If you look at the #1 of MX & VLC get requests, both MX & VLC has sent a GET request for the same URL.
Code:
GET: /storage_movie/1/194057/cdn2_vidcdn_pro/movie/hoaphuong/Thang%206/1.6/Watch%20World%20of%20Dance%20-%20Season%202%20For%20Free%20On%20yesmovies.to.mp4
HOST: cdn.vidnode.net
If you look at the Server Reply, Both has returned with 302 (i.e redirection). But with the different target location
For VLC, the server has returned with a valid video URL which is same as what we are receiving on our mobiles.
Code:
Location: https://video.xx.fbcdn.net/v/t42.9040-2/10000000_403505290165887_8647744692890370048_n.mp4?_nc_cat=0&efg=eyJybHIiOjIwMDUsInJsYSI6NDA5NiwidmVuY29kZV90YWciOiJzdmVfaGQifQ%3D%3D&rl=2005&vabr=1337&oh=70cdf02f8b7a517206ca3be7918d6a2e&oe=5B18F57C
But, For MX, the server has returned with a URL which does not exist.
Code:
Location: http://cdn16.micetop.us/cdn2_vidcdn_pro/movie/hoaphuong/Thang 6/1.6/Watch World of Dance - Season 2 For Free On yesmovies.to.mp4
Then both VLC & MX has tried whatever URL it has received. As VLC has received a valid URL, it has played the file. But, MX has received an invalid URL. So, it has failed to play.

Can you provide the actual source of the URLs?
MX Player API allows passing any HTTP headers which are required for the connection. The application which calls MX through intents sends the referer as "https://vidnode.net/". When MX Passes the received referer on the GET request, the server returns with the invalid redirection URL. If there is no referer is passed on the headers, server properly returns the valid URL.

So, there might be some configs on the server which decides the redirection URL based on the Referer. We are not sure whether it's intentional or mistake.

So, it is something that has to be fixed on the app which calls MX Player or on the server end. We can't drop the HTTP referer on the GET requests as it will break the apps that genuinely rely on it.

You can confirm this by directly inputting the URL on the MX Player's network stream option.
Code:
http://cdn.vidnode.net/storage_movie/1/194057/cdn2_vidcdn_pro/movie/hoaphuong/Thang%206/1.6/Watch%20World%20of%20Dance%20-%20Season%202%20For%20Free%20On%20yesmovies.to.mp4
If this works, Kindly contact the app developer of the parent app which is calling the MX.
The Following User Says Thank You to Thirumalai.K For This Useful Post: [ View ] Gift Thirumalai.K Ad-Free
5th June 2018, 03:59 PM |#14  
TheFixItMan's Avatar
OP Senior Member
Flag London
Thanks Meter: 3,549
 
More
Quote:
Originally Posted by Thirumalai.K

Thanks for your efforts.
In fact, MX has tried the redirected URL. It looks like a server side restriction as we have expected.

If you look at the #1 of MX & VLC get requests, both MX & VLC has sent a GET request for the same URL.

Code:
GET: /storage_movie/1/194057/cdn2_vidcdn_pro/movie/hoaphuong/Thang%206/1.6/Watch%20World%20of%20Dance%20-%20Season%202%20For%20Free%20On%20yesmovies.to.mp4
HOST: cdn.vidnode.net
If you look at the Server Reply, Both has returned with 302 (i.e redirection). But with the different target location
For VLC, the server has returned with a valid video URL which is same as what we are receiving on our mobiles.
Code:
Location: https://video.xx.fbcdn.net/v/t42.9040-2/10000000_403505290165887_8647744692890370048_n.mp4?_nc_cat=0&efg=eyJybHIiOjIwMDUsInJsYSI6NDA5NiwidmVuY29kZV90YWciOiJzdmVfaGQifQ%3D%3D&rl=2005&vabr=1337&oh=70cdf02f8b7a517206ca3be7918d6a2e&oe=5B18F57C
But, For MX, the server has returned with a URL which does not exist.
Code:
Location: http://cdn16.micetop.us/cdn2_vidcdn_pro/movie/hoaphuong/Thang 6/1.6/Watch World of Dance - Season 2 For Free On yesmovies.to.mp4
Then both VLC & MX has tried whatever URL it has received. As VLC has received a valid URL, it has played the file. But, MX has received an invalid URL. So, it has failed to play.

Can you provide the actual source of the URLs?
MX Player API allows passing any HTTP headers which are required for the connection. The application which calls MX through intents sends the referer as "https://vidnode.net/". When MX Passes the received referer on the GET request, the server returns with the invalid redirection URL. If there is no referer is passed on the headers, server properly returns the valid URL.

So, there might be some configs on the server which decides the redirection URL based on the Referer. We are not sure whether it's intentional or mistake.

So, it is something that has to be fixed on the app which calls MX Player or on the server end. We can't drop the HTTP referer on the GET requests as it will break the apps that genuinely rely on it.

You can confirm this by directly inputting the URL on the MX Player's network stream option.
Code:
http://cdn.vidnode.net/storage_movie/1/194057/cdn2_vidcdn_pro/movie/hoaphuong/Thang%206/1.6/Watch%20World%20of%20Dance%20-%20Season%202%20For%20Free%20On%20yesmovies.to.mp4
If this works, Kindly contact the app developer of the parent app which is calling the MX.

Yes inputting the stream directly into mx player alows it to work

So the app that calls mx player to play the link is doing something to stop it working
It's odd because on my phone that same app which calls mx player allows it to play fine

Thanks for your help
5th June 2018, 04:41 PM |#15  
Recognized Contributor
Thanks Meter: 4,107
 
More
Quote:
Originally Posted by TheFixItMan

Yes inputting the stream directly into mx player alows it to work

So the app that calls mx player to play the link is doing something to stop it working
It's odd because on my phone that same app which calls mx player allows it to play fine

Thanks for your help

In fact, the calling app sends the full set of http headers to be used (including the user agent string). As the app has requested, It will be used on http connection despite your custom User Agent settings. You could see a Windows UA on the http logs.

As the invalid redirection URL also a media url, it could be even a conflict on server which is triggered when using the referer. So, we are not sure that whether intentionally done or not.

Btw, Can you specify the name of the app?
It will help us to provide a better support for those who has similar issues.
5th June 2018, 05:30 PM |#16  
TheFixItMan's Avatar
OP Senior Member
Flag London
Thanks Meter: 3,549
 
More
Quote:
Originally Posted by Thirumalai.K

In fact, the calling app sends the full set http headers to be used (including the user agent string). As the app has requested, It will be used on http connection despite your custom User Agent settings. You could see a Windows UA on the http logs.

As the invalid redirection URL also a media url, it could be even a conflict on server which is triggered when using the referer. So, we are not sure that whether intentionally done or not.

Btw, Can you specify the name of the app?
It will help us to provide a better support for those who has similar issues.

Imagine if there were hardly any planets in the planetarium

Bit cryptic but you should be able to work out the app from that lol as I can't post it here for obvious reasons
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes