Page 1 of 1

Cross-Origin Request Blocked

Posted: Fri May 02, 2014 12:27 am
by Bedlore
While investigating very slow page reloads Firebug is reporting the following:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://www.sipsorcery.com/callmanager. ... bread;goto. This can be fixed by moving the resource to the same domain or enabling CORS.
https://www.sipsorcery.com/callmanager. ... bread;goto
Line 0

Can anyone advise why this has started happening today?

Re: Cross-Origin Request Blocked

Posted: Fri May 02, 2014 2:09 am
by Aaron
Almost certainly due to the web site move http://blog.sipsorcery.com/?p=1002.

It could be that your browser is loading the main page from the new server and connecting to the web services on the old server or vice-versa. It should clear itself up as DNS and caches entries expire. If you want to speed it up you could try restarting your browser and/or clearing its cache.

Re: Cross-Origin Request Blocked

Posted: Fri May 02, 2014 2:16 am
by Bedlore
Thank you for the explanation Aaron.

Re: Cross-Origin Request Blocked

Posted: Mon May 05, 2014 1:43 am
by Bedlore
I've waited several days and this is still not resolved itself.

From CLI this time:
$ curl 'https://www.sipsorcery.com/callmanager. ... bread;goto'
<string xmlns="http://schemas.microsoft.com/2003/10/Se ... on/">Sorry there was an unexpected error, the web callback was not initiated.</string>

using an IP instead gets a different result:
curl 'http://67.222.131.147/callmanager.svc/w ... bread;goto'
<head><title>Document Moved</title></head>
<body><h1>Object Moved</h1>This document may be found <a HREF="http://www.sipsorcery.com/mainsite/call ... </a></body>

Changing the URL as suggested to http://www.sipsorcery.com/mainsite/call ... ebcallback makes no difference.

I'm guessing I'm not the only webcallback user in the world, so there must be something wrong in how I'm doing it, can anyone help please?

Thanks

Re: Cross-Origin Request Blocked

Posted: Mon May 05, 2014 3:54 am
by Aaron
Sorry there was a firewall port that had not been opened for the web callback service. It's fixed now. Apologies for the confusion.