Cannot listen to this live radio

[terrypin]

On the home page for Heart Radio http://www.heartsussex.co.uk/ there's a button top left to listen live. But I get 'Bad Request'. Yet if I switch to Internet Explorer it works fine. I have the latest NoScripts add-on, but used 'Temporarily allow all this page'.

--
Terry, East Grinstead, UK

[Giorgio Maone]

Please allow also "musicradio.com".
Notice that I get an ASP server error, though, so something seems to be broken on the server side too.

[Guest]

Thanks, but I have clicked 'Temporarily allow all this page'. (And I don't see any explicit mention of '"musicradio.com")

After clicking the Play arrow, the player just spins its wheel and nothing happens. I get this in the left side of the FF status bar
Transferring data from b.scorecardresearch.com...

IE works properly.

I'll try FF with NoScript disabled. To be honest, I'm considering uninstalling it anyway, as I seem to have to allow a high proportion of the sites I visit, which is getting to be a chore.

--
Terry, East Grinstead, UK

[terrypin]

I disabled NoScript, restarted FF and tried again, but the problem remained. So it's not down to NoScript. Yet IE works solidly every time. Some sort of HTML issue?

I'll try contacting the site manager.

--
Terry, East Grinstead, UK

[terrypin]

Please allow also "musicradio.com".
Notice that I get an ASP server error, though, so something seems to be broken on the server side too.

Giorgio: musicradio.com is already in the 'whitelist', yet I still have the problem.

Sometimes the player spins its wheel for 1-2 minutes and then starts playing, and sometimes it never starts playing.

I had an email from Heart saying '...that has now been resolved and normal service has been restored,' but no details. And not fixed here!

--
Terry, East Grinstead, UK

[Giorgio Maone]

Please allow also "musicradio.com".
Notice that I get an ASP server error, though, so something seems to be broken on the server side too.

Giorgio: musicradio.com is already in the 'whitelist', yet I still have the problem.

You already said the problem remained even if you disabled NoScript, so my previous comment about whitelisting (which is still necessary if you're using NoScript) is irrelevant to fix this issue, which appears to be a server-side problem.