@tapestry.apache.org
*Subject:* *Re: TAP5-1900 - Tapestry always uses application charset for
request encoding, should first check content-type header*
I'm talking about request body encoding.
Cheers,
Nelson.
Sent from my iPhone
On 25/04/2012, at 12:59, Massimo Lusetti mluse...@gmail.com wrote:
On Wed, Apr
+1
On 25.04.2012 07:34, Igor Drobiazko wrote:
Hi Nelson,
seems to be a good idea. Any objections by others?
On Mon, Apr 23, 2012 at 3:51 PM, Nelson Rodrigues
nel...@nelsonjrodrigues.com wrote:
Hello Devs,
Before starting I'd like to acknowledge I did not read the the Getting
Involved
On Wed, Apr 25, 2012 at 7:34 AM, Igor Drobiazko
igor.drobia...@gmail.com wrote:
seems to be a good idea. Any objections by others?
Are we talking about request string parameters or the whole request
processing? I'm not in front of the code, just wondering.
Cheers
--
Massimo
I'm talking about request body encoding.
Cheers,
Nelson.
Sent from my iPhone
On 25/04/2012, at 12:59, Massimo Lusetti mluse...@gmail.com wrote:
On Wed, Apr 25, 2012 at 7:34 AM, Igor Drobiazko
igor.drobia...@gmail.com wrote:
seems to be a good idea. Any objections by others?
Are we
Hi Nelson,
seems to be a good idea. Any objections by others?
On Mon, Apr 23, 2012 at 3:51 PM, Nelson Rodrigues
nel...@nelsonjrodrigues.com wrote:
Hello Devs,
Before starting I'd like to acknowledge I did not read the the Getting
Involved section in the Community page on Tapestry's site
Hello Devs,
Before starting I'd like to acknowledge I did not read the the Getting
Involved section in the Community page on Tapestry's site and therefore did
not discuss with you guys a problem I was having before posting a Jira
issue.
That out of the way, and since it seems a 5.3.4 release is
