You're talking about someone installing some malicious firefox plugin to read incoming and outgoing data? I believe that would definitely be beyond the scope of GWT or any webpage to prevent. Much in the same way that GWT couldn't prevent a keylogger from intercepting your keystrokes.
What makes GWT-RPC any less secure than a straight HTTP post? On Oct 13, 10:17 am, JuDaC <[email protected]> wrote: > Jeff, this problem is after the submit and before the SSL. > > Just like firebug. any attacker can easily put and plugging up to your > browser (i.e FF), that you think this only make possible to download > youtube movies, but it does more than that. It intercept you > submission before it reaches the SSL. (Just like FireBug). -- 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.
