Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4B8D7BE0.5060601@christopherschultz.net>
Date: Tue, 02 Mar 2010 15:58:08 -0500
From: Christopher Schultz <chris@christopherschultz.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
 rv:1.9.1.8) Gecko/20100216 Thunderbird/3.0.2
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: unified doXXX()
References: <4B89CE2A.3000104@gmail.com> <4B8A8B17.2050200@pidster.com>
 <4B8B744C.9080608@gmail.com> <4B8BA461.10906@apache.org>
 <4B8CB569.3070507@gmail.com> <4B8D5384.3060400@christopherschultz.net>
 <4B8D6511.3070104@gmail.com> <4B8D78A6.7010001@christopherschultz.net>
 <4B8D79A4.6080604@gmail.com>
In-Reply-To: <4B8D79A4.6080604@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aryeh,

On 3/2/2010 3:48 PM, Aryeh M. Friedman wrote:
> Christopher Schultz wrote:
>
>> Is this a new client, or just a new data format? Mark's suggestion that
>> you may be using POST without the proper Content-Type would result in
>> getting null for this parameter (because Tomcat will not parse it for
>> you). If this is the case, you should either fix the new client to use
>> the proper Content-Type, or fall-back to reading and parsing the request
>> body manually when these requirements are not met.
>>   
> 
> New format same frontend client code which does use the proper content
> type. (the content type is defined at a lower level then the format and
> that code has not changed [using firebug on firefox confirms that fact])

Hmm.

So, POST + application/x-www-form-urlencoded yields a null parameter
with your new payload?

I know this sounds silly, but we're getting down to the
grasping-at-straws level, here, so bear with me: have you checked to see
that your request body is actually in the correct format (that is,
urlencoded, etc.)? I haven't looked at the Tomcat code, but Tomcat might
give up if the request body is not parsable.

Have you tried calling request.getInputStream and dumping the request
body when the parameter is null? That might give you some indication of
what's happening.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuNe+AACgkQ9CaO5/Lv0PArcwCdHf9ddwqWTKkoYb0jA9BHDs+/
LUoAnj6gNWY5mdPoCAxmgfKceWxSBy6r
=wn5q
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org