Here are my first findings:
They have different "tid" across their site. They return different parameters.
I tried :
http://uk.play.tv/player/play/i24-ne...ls&language=en with curl :
Code:
* Trying 89.202.139.130...
* TCP_NODELAY set
* Connected to uk.play.tv (89.202.139.130) port 80 (#0)
> GET /player/play/i24-news-uk/?format=hls&language=en HTTP/1.1
> Host: uk.play.tv
> Accept: */*
> User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:64.0) Gecko/20100101 Firefox/64.0
>
< HTTP/1.1 200 OK
< Server: nginx
< Date: Mon, 28 Jan 2019 18:51:27 GMT
< Content-Type: application/octet-stream
< Transfer-Encoding: chunked
< Connection: keep-alive
< Set-Cookie: __ptv_session=lb4n3kfvggrvdgbgnl7ch1ol15; path=/; domain=.play.tv; HttpOnly
< Cache-Control: no-cache, private
< X-PTV-Node: 19
< Content-Language: en_GB
< X-Robots-Tag: noindex
< X-Request-Id: 1443f08e-e7be-4f8b-94ff-0759abf5089f
<
eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1cmwiOiJodHRwczpcL1wvZWRnZS0wMi5wbGF5bWVkaWEtY2RuLm5ldFwvb3JpZ2luMDJcL2FtbHN0OmkyNC1lbmdcL3BsYXlsaXN0Lm0zdTg_ZGFyPXdzJnQ9MThkZGYxYjExZmYwZmJiMjc2NTlhMjY1YjM5ZDExMjYzYTk2ZjUxZDg5MDg1Y2E1NjAyYmJlMWIyY2I3ZjJhZGNmZDZiMDk4MDk0N2Y3YTY4NDE1MDk2YmI3Yjg3MjhmY2U3ZjE0OGIzMGY5YWJlMTcwMDdjMDg2OGNhN2RhNGJkZWNlMWVlYzM5MTc3YTJjOWQ1M2VhNWM1OTY1YTA1NzNmMzkzOWE4MzMwNjhiZmVjODUxZWZjNTdjYzFlMDQ0NmZiNmEyNjMzOGU4ZWZjNWM5NzI3YTc1Nzg1NDlhNTYwNTE4MzgzZjZlYTA3MTk3NGRhNTRmZjBiMGQ4MzM3YTczYzg5MTljYzQyNTg0YzdlMzAwZTcxN2Q4YThiN2QwMDlkZTUwMGQ5ZGI2YTgwYjYwNTgyNjRlZjUxNDExMzA1NGNjZjg1Y2EyZjA5OGZmYjBhNjQ1NjA0NDdmMjEwYSJ9.Il5tHSB8CYsYl1sQF62tng7kZ3N2m32CRicYPkLmK3E* Connection #0 to host uk.play.tv left intact
Press any key to continue . . .
Then decoded that "tid" with
https://www.base64decode.org/ :
To automate this I'll need command line tool to "base64decode".
Maybe "base64decode" isn't the best tool, you see some part of decoded url in machine code.
Very good starting point. So long for today.