Hi, Just in case : we had quite the same problem one year ago, but only with IE over https. We finally found the following solution (Apache configuration) :
SetEnvIf User-Agent ".*MSIE.*" \ nokeepalive ssl-unclean-shutdown \ downgrade-1.0 force-response-1.0 It seems that this solution has a small impact on performances, but that's the only way we found to fix this issue. Hope it helps. Johann On Dec 3, 5:06 pm, marcelstoer <[EMAIL PROTECTED]> wrote: > On Dec 2, 10:13 am, Amit Kasher <[EMAIL PROTECTED]> wrote: > > > Hi, > > Does anyone has any new insights about this issue? We've been > > investigating for over a year(!), and we seem to not be the only > > ones... > > >http://tinyurl.com/5rqfp5 > > I was recently confronted with the very same exception but in a > slightly different context. > I implemented a Servlet listener that parsed the request before it was > being forwarded through the filter chain to the GWT RPC Servlet. At > the beginning I wasn't careful enough and tinkered with the request a > bit too much, GWT doesn't like that. I now use the GWT RPC and > RPCServletUtils classes to parse the request instead of doing it > myself. > > HTH, > Marcel --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
