Yes, 
 I Spotted it and since in that method RequestEntity is not checked for
null.
so again the EncodingUrl is called.
Had   RequestEntity != null
      the Post might be bit fast.

Roland Weber-3 wrote:
> 
> Bala mani wrote:
>> Hi during Post opeartion,
>>        the doFormUrlEncode function of EncodingUtil class is called
>> twice.
> 
> Are you calling postMethod.getRequestEntity() from your application?
> It is the only call I could find where the request entity is not
> cached in an attribute once it's generated.
> 
> Please file a bug report in JIRA:
> https://issues.apache.org/jira/browse/HTTPCLIENT
> 
> cheers,
>   Roland
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/During-the-Post-operation-doFormUrlEncode-in-EncodingUtil-is-called-twice.-tf4211446.html#a12051116
Sent from the HttpClient-User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to