RPCs are gzipped only if the payload is large enough to be worth the
effort. So I'd say that only large RPC responses get gzipped, and your
application fails on large RPC responses. So there are two
possibilities:
1. You application cannot digest the response. Version missmatch? A
technical error on the client side (what's the stacktrace)?
2. The HTTP headers that indicate that the response is gzipped is lost
somewhere on the way. Does a servlet filter or web proxy eat them up?
On Jan 7, 4:04 pm, bconoly bcon...@gmail.com wrote:
Hey All,
I've been using gwt and it's rpc requests for a while. All of a
sudden some of my request started failing when everything on the
server completed perfectly. After a while I checked firebug and the
responses I'm getting back are sometimes gzipped and sometimes not.
The problem is that any time the response is gzipped my widget doing
the request doesn't load. I can only recreate this in FF, and can't
seem to do so in IE. Does anyone know why this would be?
Thanks in advance
--
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-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
