I don't claim to fully understand the request object, but as far as I can tell, the request object is the AJAX request (so for instance, request.getURL() will return "/gwtRequest". We need the URL for the page itself. Previously, I was just passing a placeholder to the authentication system, and then, on the client side, swapping that placeholder out for the current location before I did the redirect. However, in the "real" authentication system, the redirect URL is signed, so you you can't mess with it.
- Unnur On Wed, Aug 4, 2010 at 2:45 PM, <[email protected]> wrote: > It's kind of surprising that the client is responsible for telling the > server what URL it's coming from. And why aren't the header and the > request parameter redundant? > > > http://gwt-code-reviews.appspot.com/740801/show > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
