You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by Anton Tanasenko <an...@jawilla.com> on 2009/04/24 15:57:25 UTC
[Asyncweb] form-urlencoded
Hello again,
DefaultHttpRequest.setContent(IoBuffer) fails to read
x-www-form-urlencoded data if content type header also contains charset.
Example: Content-type: application/x-www-form-urlencoded; charset=utf-8.
Patch with a fix included.
Form presence clears get parameters. Is that intentional? I didn't find
anything that states get and post should be mutually exclusive.
Re : [Asyncweb] form-urlencoded
Posted by Edouard De Oliveira <do...@yahoo.fr>.
Hi Anton,
Could you please fill some JIRA's to track the two issues you raised ?
Cordialement, Regards,
-Edouard De Oliveira-
Blog: http://tedorgwp.free.fr
WebSite: http://tedorg.free.fr/en/main.php
----- Message d'origine ----
De : Anton Tanasenko <an...@jawilla.com>
À : dev@mina.apache.org
Envoyé le : Vendredi, 24 Avril 2009, 15h57mn 25s
Objet : [Asyncweb] form-urlencoded
Hello again,
DefaultHttpRequest.setContent(IoBuffer) fails to read x-www-form-urlencoded data if content type header also contains charset.
Example: Content-type: application/x-www-form-urlencoded; charset=utf-8.
Patch with a fix included.
Form presence clears get parameters. Is that intentional? I didn't find anything that states get and post should be mutually exclusive.
Re: [Asyncweb] form-urlencoded
Posted by Julien Vermillard <jv...@archean.fr>.
Le Fri, 24 Apr 2009 16:57:25 +0300,
Anton Tanasenko <an...@jawilla.com> a écrit :
> Hello again,
>
> DefaultHttpRequest.setContent(IoBuffer) fails to read
> x-www-form-urlencoded data if content type header also contains
> charset. Example: Content-type: application/x-www-form-urlencoded;
> charset=utf-8. Patch with a fix included.
>
> Form presence clears get parameters. Is that intentional? I didn't
> find anything that states get and post should be mutually exclusive.
Look like good fix, going to apply it.
Julien