Skip to content
This repository has been archived by the owner on Jun 25, 2022. It is now read-only.

Error: Parse Error #28

Open
ghost opened this issue Dec 29, 2015 · 2 comments
Open

Error: Parse Error #28

ghost opened this issue Dec 29, 2015 · 2 comments
Labels

Comments

@ghost
Copy link

ghost commented Dec 29, 2015

Hello,

I have some parse error with some SHOUTcast servers, examples:

http://crossorigin.me/http://198.50.246.192:9903/7.html
http://crossorigin.me/http://38.110.126.103:1448/index.html

Working example: http://crossorigin.me/http://206.190.143.197:8113/index.html

What's the problem ?

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/29469441-error-parse-error?utm_campaign=plugin&utm_content=tracker%2F12536595&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F12536595&utm_medium=issues&utm_source=github).
@hyperobject
Copy link
Owner

Not sure - it looks like there's something wrong with the SHOUTcast servers themselves (I'm getting a socket error on the bad URLs).

@hyperobject hyperobject added the bug label Jan 5, 2016
@ghost
Copy link
Author

ghost commented Jan 5, 2016

Maybe it seems the error happens for SHOUTcast V1 servers only, I have another CORS proxy server based on cors-anywhere ( https://calm-cliffs-9891.herokuapp.com/ )

https://calm-cliffs-9891.herokuapp.com/http://198.50.246.192:9903/7.html

No errors for me

Note: When i have the parse error ( 500 ) with crossorigin.me, the XHR.onerror() isn't triggered,
The XHR.onload() still triggers with a responseText " Error: Error: Parse Error "

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant