Safari and response header

[hbjornev]

There has been an update at a point where Safari no longer accepts HTTP version 0.9. If it finds something that looks like 0.9, then put the contents in "sandbox" mode - some crappy mode where things do not work as it should.
*
The problem now is that streaming radio server returns content that do not specify HTTP version and Safari when thinking that it is HTTP / 0.9.
*
Are there opportunities to modify the response head the clean from the server, so that when we ask http://159.253.131.114:8140 and http://159.253.131.114:8168 about content, the server can specify eksplitist
HTTP / 1.1 200 OK
*
Otherwise I'm not quite sure how we'd gotten radio to funke sites right now (In Safari then)

[irca]

Also coming up against this.

Did you find a solution?

[antonkeren]

The issue will likely be more prominent, as the same behaviour has been sighted on Chrome 55, that will be released early December.

See:
http://forums.shoutcast.com/showthre...39#post3074439