i dont think u can do this at js in dom. browser handles this automatically when it sees the http-auth-required header before your js-code gets it. u'll need an anternative approach for this
On Wed, Jun 29, 2011 at 7:52 PM, objectuser <[email protected]> wrote: > I'm not an expert in this by any means (and certainly don't know your > requirements), but it seems like basic auth is fundamentally incompatible > with a GWT app (or at least the portion you describe). > > I think a more compatible model would be to rely on something like cookies, > have a particular service that does not require authentication, and then > check the response to that to see if the user is authenticated. Then you > can put access control on all your other services to ensure authenticated > access. > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/HrYT7hSLoX0J. > To post to this group, send email to [email protected]. > 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. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. 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.
