Open ajeje989 opened 1 year ago
a few things were fixed post kh17, latest master contains all fixes, but those 2 urls looks to have to same info with respect to CORS. Are you sure it is cors related?
karl
in the version Icecast 2.4.0-kh15-ac1 ( add on azuracast 0.17.6 )
work fine
i thinks is a problem with link:port
ok, so let me know what the difference is between kh15-ac1 (I presume modified) and kh17
@ajeje989 I see the latest Azuracast rolling release already uses kh18, maybe you can try it I open and play url you run smoothly in my player and browser https://azura.servertec85.com:8090/radio.mp3 https://azura.servertec85.com/radio/8090/radio.mp3
@ajeje989 I see the latest Azuracast rolling release already uses kh18, maybe you can try it I open and play url you run smoothly in my player and browser https://azura.servertec85.com:8090/radio.mp3 https://azura.servertec85.com/radio/8090/radio.mp3
the rolling release not tried sincerely.
the music listen well even in the latest version it is the cors that no longer works with ip:port and I don't understand the reason
99,9% is a problem with kh17 because with kh15 works
Can you compare the headers you get from kh17 against the ones from kh15-ac1. Let us see what is different
karl
is this still an issue with kh18.3?
karl
is this still an issue with kh18.3?
karl
i don't know because i use azuracast last stable version
kh18.3 has a problem when testing on centova, after streaming for more than 8 hours, the icecast service is off and you have to restart the station.
I doubt that would be a CORS related issue though. Obviously any stability issue should be reported in detail though
karl.
hi in this version if i use my cors ( cors anyhwere ) not work
example with last version azuracast 0.17.7 ( they use Icecast 2.4.0-kh17 )
this not work https://azura.servertec85.com:8090/
this work https://azura.servertec85.com/radio/8090/
Maybe it's the new version of Icecast 2.4.0-kh17 that creates this conflict.
Is it possible to know if it has been fixed in the new release?