I'm hitting the same problem with 1.5.3 as well. Now, I'm forced to
use the -noserver mode. I hope that same policy origin check can be
removed from the latest build.
On Oct 21, 8:47 pm, Brian <[EMAIL PROTECTED]> wrote:
> Here's code to demonstrate 1.5.3 causing a same-origin security
> restriction exception, which does not occur in 1.5.2. I'm testing in
> hosted mode on port 8888, running under windows vista. You don't need
> anything to be running on port 8080 for this test (but that's where my
> server normally runs).
> Running this code on gwt 1.5.2 just exits cleanly. With 1.5.3, the
> Widow.alert() in the try/catch handler is executed.
>
> public class Xsstest implements EntryPoint {
> public void onModuleLoad() {
> RequestBuilder rb = new RequestBuilder(RequestBuilder.POST,
> "http://localhost:8080/v1";);
> rb.setTimeoutMillis(5000);
> rb.setHeader("If-Modified-Since", "" + new Date(0));
> rb.setHeader("Content-type", "application/x-www-form-
> urlencoded");
> rb.setHeader("Connection", "close");
> try {
> rb.sendRequest("test", new RequestCallback(){
> public void onResponseReceived(Request request,
> Response response) {
> }
>
> public void onError(Request request, Throwable
> exception) {
> }
> });
> } catch (Exception e) {
> // this is hit in 1.5.3, not 1.5.2:
> Window.alert(e.getMessage());
> }
> }
>
> }
>
> On Oct 20, 1:15 pm, Brian <[EMAIL PROTECTED]> wrote:
>
> > I'm seeing a same-origin security restriction exception in 1.5.3 where
> > I didn't see it in 1.5.2. That is, I can switch my project back and
> > forth between using 1.5.2 (no exception) and 1.5.3 (exception), with
> > the same source code.
>
> > I'm doing a RequestBuilder to "locahost:8080/url" in order to hit my
> > server to POST some data.
>
> > Means I'll be using 1.5.2 until I can figure out how to hit my local
> > server from 1.5.3.
>
> > Brian
>
> > On Oct 20, 11:17 am, "nicolas.deloof" <[EMAIL PROTECTED]>
> > wrote:
>
> > > Hi,
>
> > > for maven users, this release will be available via maven central
> > > repository in few hours (after rsync does its job).
>
> > > Nicolas
>
> > > On 18 oct, 00:22, Ray Ryan <[EMAIL PROTECTED]> wrote:
>
> > > > Hi, all.
>
> > > > We have just deprecated GWT 1.5.2, and replaced it with GWT 1.5.3.
> > > > This new release has a small handful of patches, mainly aimed at
> > > > fixing RPC problems with Android. You can download the update from the
> > > > usual location:
>
> > > > http://code.google.com/webtoolkit/download.html
>
> > > > You may find that this pretty page hasn't updated yet in your neck of
> > > > the woods. If so, try going straight to the download
> > > > server:http://code.google.com/p/google-web-toolkit/downloads/list.
>
> > > > Enjoy,
> > > > rjrjr
>
> > > > Release Notes for 1.5.3
>
> > > > Fixed Issues
>
> > > > - RPC requests no longer fail on the embedded Android web browser
>
> > > > - Leaf TreeItems now line up with their non-leaf siblings
>
> > > > - Removing the last child node from a TreeItem no longer creates
> > > > extra margins on the left
>
> > > > - HTTPRequest no longer uses POST instead of GET on some IE installs
> > > > because of incorrect XHR selection
>
> > > > - Compiler now uses a more reliable check to prevent methods with
> > > > local variables from being inlined
> > > > getAbsoluteTop()/Left() can no longer return non-integral values
>
> > > > - Time.valueOf() no longer fails to parse "08:00:00" or incorrectly
> > > > accepts "0xC:0xB:0xA".
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
