Installation Method
Docker Installation
AzuraCast Release Channel
Stable Channel
Current AzuraCast Version
0.18.5
What happened?
Hi,
Previoulsy in 0.17.7 Stable, I was using http://domain.name:station_port/status-json.xsl of an "offline" station (just used as icecast server for animators that RadioDJ listen when animator do a live), to get active mount points ("listenurl" key), to allow animator to enqueue its live track in RadioDJ only if he sends its stream.
I use php file_get_contents and parse the array. With some other code lines, I create an array with some datas. This php page is called from an AJAX request.
This night, I decided to update AzuraCast.
Since, the file_get_contents takes around 10 seconds to get the xsl file .
If I open the file directly with the link in the browser, it generates the file.json file without delay.
If I replace http or https, the file_get_contents function gets the file without delay.
In my case, changing http for https should be the workaround, but it could be a problem for who is using http only.
Couin :)
Relevant log output
No response
Installation Method
Docker Installation
AzuraCast Release Channel
Stable Channel
Current AzuraCast Version
0.18.5
What happened?
Hi,
Previoulsy in 0.17.7 Stable, I was using http://domain.name:station_port/status-json.xsl of an "offline" station (just used as icecast server for animators that RadioDJ listen when animator do a live), to get active mount points ("listenurl" key), to allow animator to enqueue its live track in RadioDJ only if he sends its stream.
I use php file_get_contents and parse the array. With some other code lines, I create an array with some datas. This php page is called from an AJAX request.
This night, I decided to update AzuraCast.
Since, the file_get_contents takes around 10 seconds to get the xsl file .
If I open the file directly with the link in the browser, it generates the file.json file without delay.
If I replace http or https, the file_get_contents function gets the file without delay.
In my case, changing http for https should be the workaround, but it could be a problem for who is using http only.
Couin :)
Relevant log output
No response