Re: How to solve RPC error: Character Encoding is 'text/'. Expected 'UTF-8'

2016-01-16 Thread Hua Zhang
I have the same issue and just verified how it happens. I compare the tomcat log file with the tomcat access log file 66.249.88.115 - - [15/Jan/2016:09:09:20 +0100] "POST /datalint/service/user HTTP/1.1" 500 57 66.249.88.95 - - [15/Jan/2016:09:09:21 +0100] "POST /datalint/service/user

How to solve RPC error: Character Encoding is 'text/'. Expected 'UTF-8'

2015-12-30 Thread Ed
Sometimes I do get the following stacktrace during RPC communication with the Tomcat backend. Any idea how to solve this, and what could cause this ? - Ed javax.servlet.ServletException: Character Encoding is 'text/'. Expected 'UTF-8' at

Re: How to solve RPC error: Character Encoding is 'text/'. Expected 'UTF-8'

2015-12-30 Thread Thomas Broyer
Somehow your HttpServletRequest is "broken" and returns "text/" as character encoding: https://github.com/gwtproject/gwt/blob/ad8ed35116bf22efdfdcf6984a3a3d79e26ded04/user/src/com/google/gwt/user/server/rpc/RPCServletUtils.java#L425 This might be due either to bad parsing somewhere (Tomcat?), a

Re: How to solve RPC error: Character Encoding is 'text/'. Expected 'UTF-8'

2015-12-30 Thread Ed Bras
@Thomas: thanks for the tips, I will perform some logging of the Content-Type to see where it's coming from.​ -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to