08.08.2010, 15:42
(01.07.2010, 17:42)hvdwolf Wrote:(30.06.2010, 21:57)routeconverter Wrote:(20.06.2010, 16:23)routeconverter Wrote: Of course - that's related to problem with the unreachable port. Something is blocking the web browser (I guess it's a Web Kit-based component) to direct AJAX-calls to the port from the RouteConverter process.
I found out, what the for this behaviour is: the error is NS_ERROR_DOM_BAD_URI and the cause is the same origin policy that changed between XUL Runner 1.8 and 1.9 as explained here.
Firefox 3.6.6 is my default browser on Apple. I went into firefox and in the address bar I added the "about:config" address (without the double quotes) to get to the advanced settings.
In the command bar I added the mentioned "security.fileuri.strict_origin_policy" and it was set to true. I changed it to false. I stopped Firefox and started it to verify: It was still at false. I started RouteConverter but it still gives the same error when accessing the internal port.
Note: I also switched to Safari and Google Chrome much earlier and they had the same error.
Coming back on this: Is there anything I can do to help you with this? Things I could try on either Linux or MacOSX?
I assume you use XUL runner inside RouteConverter but where?
I changed the relevant settings on my Mac and my linux box, so it should be inside Routeconverter, or not?
