Hi Danny,

The issue you ran into is not actually a bug but an improvement in 1.5.3 in
terms of browser security compliance.

Basically, the remote data you are fetching is indeed violating the single
origin policy, which is why you are seeing the error message come up in the
hosted mode console.

The two ways to enable cross-site communication would be to use -noserver
with a proxy that could delegate the calls or using the JSONP technique.
Both are described in a bit more detail on the Groups post linked below:

http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/48413bdb6e5b292#msg_71f28d8b382e7f04

Hope that helps,
-Sumit Chandel

On Thu, Nov 13, 2008 at 5:05 PM, Danny <[EMAIL PROTECTED]> wrote:

>
> Just thought I'd post an update...
>
> I downgraded from 1.5.3 to 1.5.2 and its now working so I guess this
> is a bug with 1.5.3.
>
> Regards,
> Danny
>
> On Nov 14, 12:40 am, Danny <[EMAIL PROTECTED]> wrote:
> > Hi All,
> >
> > I finally got round to making my app run in 1.5 and all is looking
> > good.  However I often use hosted mode with remote data, which helps
> > massively when debugging issues.  I am using RequestBuilder.
> >
> > I'm getting a weird error in 1.5, if I switch back to 1.4 it works
> > perfectly.  I get the following when in hosted mode.
> >
> > The URLhttp://x.x.x.x/yyyy.zzzis invalid or violates the same-origin
> > security restriction
> >
> > I've enabled cross-brower communication in Internet Explorer and added
> > the site to my Local Intranet, but still not joy.
> >
> > Can anyone shed any light on this?
> >
> > Many thanks,
> > Danny
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to