RE: Re: Post method not work when deployed to GAE

I forgot to say that the fix is available in the current snapshot and will be part of the 2.1m4 release. Best regards, Thierry Boileau -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2724966

RE: Re: Post method not work when deployed to GAE

Hello all, the now closed issue 1219 [1] described the solution to this issue. In a few words, a new boolean attribute called "entityBuffering" has been added to the ClientResource class. When set to "true", the entity is first stored in memory then sent to the GAE server. Best regards, Thier

RE: Re: Post method not work when deployed to GAE

Hello Joe, I've found what happens. The servlet container modifies the headers when the incoming entity is chunked. It removes the "Transfer-Encoding: chunked" header, which leads to a wrong interpretation of the incoming entity (see ServerCall#getRequestEntity method). I wonder if we can updat

RE: Re: Post method not work when deployed to GAE

Hi Thierry, As I pointed out in a previous posting I noticed a difference in the HTTP-Params of the Headers while requesting for ex. with curl and using the "wrap"-Method. Is it an option to just use the header that's working? Remember that deserializing works, generally... Cheers, Joe -