Discussion:
MultipartEntityBuilder and Charset US-ASCII
Philippe Mouawad
2017-04-17 20:50:43 UTC
Permalink
Hello,
At JMeter we have a bug report (
https://bz.apache.org/bugzilla/show_bug.cgi?id=60800) related to Multipart
Form POST request

A user reports that he has an issue with a request created by JMeter due to
the presence in Request Headers of "charset=US-ASCII" at end of boundary in
Content-Type.

------------------------------------------------------------------------
POST http://localhost:8081/

POST data:
--5v5So93EEOXPO8DIg4kmR-vfmsbimn
Content-Disposition: form-data; name="toto"

titi
--5v5So93EEOXPO8DIg4kmR-vfmsbimn--


*Request Headers:*
Connection: keep-alive
Content-Length: 123
*Content-Type: multipart/form-data;
boundary=5v5So93EEOXPO8DIg4kmR-vfmsbimn; charset=US-ASCII*
Host: localhost:8081
User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_121)

------------------------------------------------------------------------

The code is created through (
https://github.com/apache/jmeter/blob/trunk/src/protocol/http/org/apache/jmeter/protocol/http/sampler/HTTPHC4Impl.java#L1201
):

1/ MultipartEntityBuilder multipartEntityBuilder =
MultipartEntityBuilder.create();

2/ As not Content Type is set in GUI, we default to US-ASCII so call:
multipartEntityBuilder.setCharset("US-ASCII");

3/
multipartEntityBuilder.setLaxMode();

4/ For every parameter:
StringBody stringBody = new StringBody(arg.getValue(),
ContentType.create("text/plain", charset));
FormBodyPart formPart = FormBodyPartBuilder.create(
parameterName, stringBody).build();
multipartEntityBuilder.addPart(formPart);

5/
HttpEntity entity = multipartEntityBuilder.build();
post.setEntity(entity);


So my questions are the following:
1/ Is it correct to add this charset part ?
2/ Could you point me to the reference part of RFC that mentions this ?
3/ Is it correct to avoid setting charset in this case in API which would
lead to such request instead ?



POST http://localhost:8081/

POST data:
--xjNHd_UhEEpqC2ZoFCpGRzYzHK90ljsdpfTr
Content-Disposition: form-data; name="toto"

titi
--xjNHd_UhEEpqC2ZoFCpGRzYzHK90ljsdpfTr--

Request Headers:
Connection: keep-alive
Content-Length: 135
Content-Type: multipart/form-data;
boundary=xjNHd_UhEEpqC2ZoFCpGRzYzHK90ljsdpfTr
Host: localhost:8081
User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_121)


Thanks for your help
Regards
Philippe M.
Philippe Mouawad
2017-04-19 20:23:47 UTC
Permalink
Hello,
Anybody has an idea about that ?
Thanks

On Mon, Apr 17, 2017 at 10:50 PM, Philippe Mouawad <
Post by Philippe Mouawad
Hello,
At JMeter we have a bug report (https://bz.apache.org/
bugzilla/show_bug.cgi?id=60800) related to Multipart Form POST request
A user reports that he has an issue with a request created by JMeter due
to the presence in Request Headers of "charset=US-ASCII" at end of boundary
in Content-Type.
------------------------------------------------------------------------
POST http://localhost:8081/
--5v5So93EEOXPO8DIg4kmR-vfmsbimn
Content-Disposition: form-data; name="toto"
titi
--5v5So93EEOXPO8DIg4kmR-vfmsbimn--
*Request Headers:*
Connection: keep-alive
Content-Length: 123
*Content-Type: multipart/form-data;
boundary=5v5So93EEOXPO8DIg4kmR-vfmsbimn; charset=US-ASCII*
Host: localhost:8081
User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_121)
------------------------------------------------------------------------
The code is created through (https://github.com/apache/
jmeter/blob/trunk/src/protocol/http/org/apache/
1/ MultipartEntityBuilder multipartEntityBuilder =
MultipartEntityBuilder.create();
multipartEntityBuilder.setCharset("US-ASCII");
3/
multipartEntityBuilder.setLaxMode();
StringBody stringBody = new StringBody(arg.getValue(),
ContentType.create("text/plain", charset));
FormBodyPart formPart = FormBodyPartBuilder.create(
parameterName, stringBody).build();
multipartEntityBuilder.addPart(formPart);
5/
HttpEntity entity = multipartEntityBuilder.build();
post.setEntity(entity);
1/ Is it correct to add this charset part ?
2/ Could you point me to the reference part of RFC that mentions this ?
3/ Is it correct to avoid setting charset in this case in API which would
lead to such request instead ?
POST http://localhost:8081/
--xjNHd_UhEEpqC2ZoFCpGRzYzHK90ljsdpfTr
Content-Disposition: form-data; name="toto"
titi
--xjNHd_UhEEpqC2ZoFCpGRzYzHK90ljsdpfTr--
Connection: keep-alive
Content-Length: 135
Content-Type: multipart/form-data; boundary=xjNHd_
UhEEpqC2ZoFCpGRzYzHK90ljsdpfTr
Host: localhost:8081
User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_121)
Thanks for your help
Regards
Philippe M.
--
Cordialement.
Philippe Mouawad.
Philippe Mouawad
2017-05-20 14:31:16 UTC
Permalink
Hello,
Any thoughts on that ?

Thx
Post by Philippe Mouawad
Hello,
Anybody has an idea about that ?
Thanks
On Mon, Apr 17, 2017 at 10:50 PM, Philippe Mouawad <
Post by Philippe Mouawad
Hello,
At JMeter we have a bug report (https://bz.apache.org/bugzill
a/show_bug.cgi?id=60800) related to Multipart Form POST request
A user reports that he has an issue with a request created by JMeter due
to the presence in Request Headers of "charset=US-ASCII" at end of boundary
in Content-Type.
------------------------------------------------------------------------
POST http://localhost:8081/
--5v5So93EEOXPO8DIg4kmR-vfmsbimn
Content-Disposition: form-data; name="toto"
titi
--5v5So93EEOXPO8DIg4kmR-vfmsbimn--
*Request Headers:*
Connection: keep-alive
Content-Length: 123
*Content-Type: multipart/form-data;
boundary=5v5So93EEOXPO8DIg4kmR-vfmsbimn; charset=US-ASCII*
Host: localhost:8081
User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_121)
------------------------------------------------------------------------
The code is created through (https://github.com/apache/jme
ter/blob/trunk/src/protocol/http/org/apache/jmeter/
1/ MultipartEntityBuilder multipartEntityBuilder =
MultipartEntityBuilder.create();
multipartEntityBuilder.setCharset("US-ASCII");
3/
multipartEntityBuilder.setLaxMode();
StringBody stringBody = new StringBody(arg.getValue(),
ContentType.create("text/plain", charset));
FormBodyPart formPart = FormBodyPartBuilder.create(
parameterName, stringBody).build();
multipartEntityBuilder.addPart(formPart);
5/
HttpEntity entity = multipartEntityBuilder.build();
post.setEntity(entity);
1/ Is it correct to add this charset part ?
2/ Could you point me to the reference part of RFC that mentions this ?
3/ Is it correct to avoid setting charset in this case in API which would
lead to such request instead ?
POST http://localhost:8081/
--xjNHd_UhEEpqC2ZoFCpGRzYzHK90ljsdpfTr
Content-Disposition: form-data; name="toto"
titi
--xjNHd_UhEEpqC2ZoFCpGRzYzHK90ljsdpfTr--
Connection: keep-alive
Content-Length: 135
Content-Type: multipart/form-data; boundary=xjNHd_UhEEpqC2ZoFCpGR
zYzHK90ljsdpfTr
Host: localhost:8081
User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_121)
Thanks for your help
Regards
Philippe M.
--
Cordialement.
Philippe Mouawad.
--
Cordialement.
Philippe Mouawad.
Gary Gregory
2017-05-22 04:46:53 UTC
Permalink
Philippe,

Have you solved this?

Gary


On May 20, 2017 7:31 AM, "Philippe Mouawad" <***@gmail.com>
wrote:

Hello,
Any thoughts on that ?

Thx
Post by Philippe Mouawad
Hello,
Anybody has an idea about that ?
Thanks
On Mon, Apr 17, 2017 at 10:50 PM, Philippe Mouawad <
Post by Philippe Mouawad
Hello,
At JMeter we have a bug report (https://bz.apache.org/bugzill
a/show_bug.cgi?id=60800) related to Multipart Form POST request
A user reports that he has an issue with a request created by JMeter due
to the presence in Request Headers of "charset=US-ASCII" at end of boundary
in Content-Type.
------------------------------------------------------------------------
POST http://localhost:8081/
--5v5So93EEOXPO8DIg4kmR-vfmsbimn
Content-Disposition: form-data; name="toto"
titi
--5v5So93EEOXPO8DIg4kmR-vfmsbimn--
*Request Headers:*
Connection: keep-alive
Content-Length: 123
*Content-Type: multipart/form-data;
boundary=5v5So93EEOXPO8DIg4kmR-vfmsbimn; charset=US-ASCII*
Host: localhost:8081
User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_121)
------------------------------------------------------------------------
The code is created through (https://github.com/apache/jme
ter/blob/trunk/src/protocol/http/org/apache/jmeter/
1/ MultipartEntityBuilder multipartEntityBuilder =
MultipartEntityBuilder.create();
multipartEntityBuilder.setCharset("US-ASCII");
3/
multipartEntityBuilder.setLaxMode();
StringBody stringBody = new StringBody(arg.getValue(),
ContentType.create("text/plain", charset));
FormBodyPart formPart = FormBodyPartBuilder.create(
parameterName, stringBody).build();
multipartEntityBuilder.addPart(formPart);
5/
HttpEntity entity = multipartEntityBuilder.build();
post.setEntity(entity);
1/ Is it correct to add this charset part ?
2/ Could you point me to the reference part of RFC that mentions this ?
3/ Is it correct to avoid setting charset in this case in API which would
lead to such request instead ?
POST http://localhost:8081/
--xjNHd_UhEEpqC2ZoFCpGRzYzHK90ljsdpfTr
Content-Disposition: form-data; name="toto"
titi
--xjNHd_UhEEpqC2ZoFCpGRzYzHK90ljsdpfTr--
Connection: keep-alive
Content-Length: 135
Content-Type: multipart/form-data; boundary=xjNHd_UhEEpqC2ZoFCpGR
zYzHK90ljsdpfTr
Host: localhost:8081
User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_121)
Thanks for your help
Regards
Philippe M.
--
Cordialement.
Philippe Mouawad.
--
Cordialement.
Philippe Mouawad.
Philippe Mouawad
2017-05-27 22:28:19 UTC
Permalink
Hello Gary,
No unfortunately.
I was hoping to get some lights from the mailing list here.


Regards
Post by Gary Gregory
Philippe,
Have you solved this?
Gary
Hello,
Any thoughts on that ?
Thx
Post by Philippe Mouawad
Hello,
Anybody has an idea about that ?
Thanks
On Mon, Apr 17, 2017 at 10:50 PM, Philippe Mouawad <
Post by Philippe Mouawad
Hello,
At JMeter we have a bug report (https://bz.apache.org/bugzill
a/show_bug.cgi?id=60800) related to Multipart Form POST request
A user reports that he has an issue with a request created by JMeter due
to the presence in Request Headers of "charset=US-ASCII" at end of
boundary
Post by Philippe Mouawad
Post by Philippe Mouawad
in Content-Type.
------------------------------------------------------------
------------
Post by Philippe Mouawad
Post by Philippe Mouawad
POST http://localhost:8081/
--5v5So93EEOXPO8DIg4kmR-vfmsbimn
Content-Disposition: form-data; name="toto"
titi
--5v5So93EEOXPO8DIg4kmR-vfmsbimn--
*Request Headers:*
Connection: keep-alive
Content-Length: 123
*Content-Type: multipart/form-data;
boundary=5v5So93EEOXPO8DIg4kmR-vfmsbimn; charset=US-ASCII*
Host: localhost:8081
User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_121)
------------------------------------------------------------
------------
Post by Philippe Mouawad
Post by Philippe Mouawad
The code is created through (https://github.com/apache/jme
ter/blob/trunk/src/protocol/http/org/apache/jmeter/
1/ MultipartEntityBuilder multipartEntityBuilder =
MultipartEntityBuilder.create();
multipartEntityBuilder.setCharset("US-ASCII");
3/
multipartEntityBuilder.setLaxMode();
StringBody stringBody = new StringBody(arg.getValue(),
ContentType.create("text/plain", charset));
FormBodyPart formPart = FormBodyPartBuilder.create(
parameterName, stringBody).build();
multipartEntityBuilder.addPart(formPart);
5/
HttpEntity entity = multipartEntityBuilder.build();
post.setEntity(entity);
1/ Is it correct to add this charset part ?
2/ Could you point me to the reference part of RFC that mentions this ?
3/ Is it correct to avoid setting charset in this case in API which
would
Post by Philippe Mouawad
Post by Philippe Mouawad
lead to such request instead ?
POST http://localhost:8081/
--xjNHd_UhEEpqC2ZoFCpGRzYzHK90ljsdpfTr
Content-Disposition: form-data; name="toto"
titi
--xjNHd_UhEEpqC2ZoFCpGRzYzHK90ljsdpfTr--
Connection: keep-alive
Content-Length: 135
Content-Type: multipart/form-data; boundary=xjNHd_UhEEpqC2ZoFCpGR
zYzHK90ljsdpfTr
Host: localhost:8081
User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_121)
Thanks for your help
Regards
Philippe M.
--
Cordialement.
Philippe Mouawad.
--
Cordialement.
Philippe Mouawad.
--
Cordialement.
Philippe Mouawad.
Ubik-Ingénierie

UBIK LOAD PACK Web Site <http://www.ubikloadpack.com/>

UBIK LOAD PACK on TWITTER <https://twitter.com/ubikloadpack>
Oleg Kalnichevski
2017-05-28 10:43:20 UTC
Permalink
Post by Philippe Mouawad
Hello,
Any thoughts on that ?
Hi Philippe

This is perfectly legal. See

https://www.ietf.org/rfc/rfc1341.txt

Oleg
Post by Philippe Mouawad
Thx
l.com>
Post by Philippe Mouawad
Hello,
Anybody has an idea about that ?
Thanks
On Mon, Apr 17, 2017 at 10:50 PM, Philippe Mouawad <
Post by Philippe Mouawad
Hello,
At JMeter we have a bug report (https://bz.apache.org/bugzill
a/show_bug.cgi?id=60800) related to Multipart Form POST request
A user reports that he has an issue with a request created by JMeter due
to the presence in Request Headers of "charset=US-ASCII" at end of boundary
in Content-Type.
---------------------------------------------------------------
---------
POST http://localhost:8081/
--5v5So93EEOXPO8DIg4kmR-vfmsbimn
Content-Disposition: form-data; name="toto"
titi
--5v5So93EEOXPO8DIg4kmR-vfmsbimn--
*Request Headers:*
Connection: keep-alive
Content-Length: 123
*Content-Type: multipart/form-data;
boundary=5v5So93EEOXPO8DIg4kmR-vfmsbimn; charset=US-ASCII*
Host: localhost:8081
User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_121)
---------------------------------------------------------------
---------
The code is created through (https://github.com/apache/jme
ter/blob/trunk/src/protocol/http/org/apache/jmeter/
1/            MultipartEntityBuilder multipartEntityBuilder =
MultipartEntityBuilder.create();
multipartEntityBuilder.setCharset("US-ASCII");
3/
multipartEntityBuilder.setLaxMode();
                StringBody stringBody = new
StringBody(arg.getValue(),
ContentType.create("text/plain", charset));
                FormBodyPart formPart =
FormBodyPartBuilder.create(
                        parameterName, stringBody).build();
                multipartEntityBuilder.addPart(formPart);
5/
            HttpEntity entity = multipartEntityBuilder.build();
            post.setEntity(entity);
1/ Is it correct to add this charset part ?
2/ Could you point me to the reference part of RFC that mentions this ?
3/ Is it correct to avoid setting charset in this case in API which would
lead to such request instead ?
POST http://localhost:8081/
--xjNHd_UhEEpqC2ZoFCpGRzYzHK90ljsdpfTr
Content-Disposition: form-data; name="toto"
titi
--xjNHd_UhEEpqC2ZoFCpGRzYzHK90ljsdpfTr--
Connection: keep-alive
Content-Length: 135
Content-Type: multipart/form-data; boundary=xjNHd_UhEEpqC2ZoFCpGR
zYzHK90ljsdpfTr
Host: localhost:8081
User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_121)
Thanks for your help
Regards
Philippe M.
--
Cordialement.
Philippe Mouawad.
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-***@hc.apache.org
For additional commands, e-mail: httpclient-users-***@hc.apache.org
Philippe Mouawad
2017-05-28 10:47:25 UTC
Permalink
Hi Oleg,
From the 3 questions I asked, to which one are you answering ?
The first ?
If possible, can you point the paragraph ?

Thanks
Post by Oleg Kalnichevski
Post by Philippe Mouawad
Hello,
Any thoughts on that ?
Hi Philippe
This is perfectly legal. See
https://www.ietf.org/rfc/rfc1341.txt
Oleg
Post by Philippe Mouawad
Thx
l.com>
Post by Philippe Mouawad
Hello,
Anybody has an idea about that ?
Thanks
On Mon, Apr 17, 2017 at 10:50 PM, Philippe Mouawad <
<javascript:;>');>>
Post by Philippe Mouawad
Post by Philippe Mouawad
Post by Philippe Mouawad
Hello,
At JMeter we have a bug report (https://bz.apache.org/bugzill
a/show_bug.cgi?id=60800) related to Multipart Form POST request
A user reports that he has an issue with a request created by JMeter due
to the presence in Request Headers of "charset=US-ASCII" at end of boundary
in Content-Type.
---------------------------------------------------------------
---------
POST http://localhost:8081/
--5v5So93EEOXPO8DIg4kmR-vfmsbimn
Content-Disposition: form-data; name="toto"
titi
--5v5So93EEOXPO8DIg4kmR-vfmsbimn--
*Request Headers:*
Connection: keep-alive
Content-Length: 123
*Content-Type: multipart/form-data;
boundary=5v5So93EEOXPO8DIg4kmR-vfmsbimn; charset=US-ASCII*
Host: localhost:8081
User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_121)
---------------------------------------------------------------
---------
The code is created through (https://github.com/apache/jme
ter/blob/trunk/src/protocol/http/org/apache/jmeter/
1/ MultipartEntityBuilder multipartEntityBuilder =
MultipartEntityBuilder.create();
multipartEntityBuilder.setCharset("US-ASCII");
3/
multipartEntityBuilder.setLaxMode();
StringBody stringBody = new
StringBody(arg.getValue(),
ContentType.create("text/plain", charset));
FormBodyPart formPart =
FormBodyPartBuilder.create(
parameterName, stringBody).build();
multipartEntityBuilder.addPart(formPart);
5/
HttpEntity entity = multipartEntityBuilder.build();
post.setEntity(entity);
1/ Is it correct to add this charset part ?
2/ Could you point me to the reference part of RFC that mentions this ?
3/ Is it correct to avoid setting charset in this case in API which would
lead to such request instead ?
POST http://localhost:8081/
--xjNHd_UhEEpqC2ZoFCpGRzYzHK90ljsdpfTr
Content-Disposition: form-data; name="toto"
titi
--xjNHd_UhEEpqC2ZoFCpGRzYzHK90ljsdpfTr--
Connection: keep-alive
Content-Length: 135
Content-Type: multipart/form-data; boundary=xjNHd_UhEEpqC2ZoFCpGR
zYzHK90ljsdpfTr
Host: localhost:8081
User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_121)
Thanks for your help
Regards
Philippe M.
--
Cordialement.
Philippe Mouawad.
--
Cordialement.
Philippe Mouawad.
Philippe Mouawad
2017-06-03 08:51:17 UTC
Permalink
Hello,
Any answers on those questions ?

Thank you

On Sun, May 28, 2017 at 12:47 PM, Philippe Mouawad <
Post by Philippe Mouawad
Hi Oleg,
From the 3 questions I asked, to which one are you answering ?
The first ?
If possible, can you point the paragraph ?
Thanks
Post by Oleg Kalnichevski
Post by Philippe Mouawad
Hello,
Any thoughts on that ?
Hi Philippe
This is perfectly legal. See
https://www.ietf.org/rfc/rfc1341.txt
Oleg
Post by Philippe Mouawad
Thx
l.com>
Post by Philippe Mouawad
Hello,
Anybody has an idea about that ?
Thanks
On Mon, Apr 17, 2017 at 10:50 PM, Philippe Mouawad <
Post by Philippe Mouawad
Hello,
At JMeter we have a bug report (https://bz.apache.org/bugzill
a/show_bug.cgi?id=60800) related to Multipart Form POST request
A user reports that he has an issue with a request created by JMeter due
to the presence in Request Headers of "charset=US-ASCII" at end of boundary
in Content-Type.
---------------------------------------------------------------
---------
POST http://localhost:8081/
--5v5So93EEOXPO8DIg4kmR-vfmsbimn
Content-Disposition: form-data; name="toto"
titi
--5v5So93EEOXPO8DIg4kmR-vfmsbimn--
*Request Headers:*
Connection: keep-alive
Content-Length: 123
*Content-Type: multipart/form-data;
boundary=5v5So93EEOXPO8DIg4kmR-vfmsbimn; charset=US-ASCII*
Host: localhost:8081
User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_121)
---------------------------------------------------------------
---------
The code is created through (https://github.com/apache/jme
ter/blob/trunk/src/protocol/http/org/apache/jmeter/
1/ MultipartEntityBuilder multipartEntityBuilder =
MultipartEntityBuilder.create();
multipartEntityBuilder.setCharset("US-ASCII");
3/
multipartEntityBuilder.setLaxMode();
StringBody stringBody = new
StringBody(arg.getValue(),
ContentType.create("text/plain", charset));
FormBodyPart formPart =
FormBodyPartBuilder.create(
parameterName, stringBody).build();
multipartEntityBuilder.addPart(formPart);
5/
HttpEntity entity = multipartEntityBuilder.build();
post.setEntity(entity);
1/ Is it correct to add this charset part ?
2/ Could you point me to the reference part of RFC that mentions this ?
3/ Is it correct to avoid setting charset in this case in API which would
lead to such request instead ?
POST http://localhost:8081/
--xjNHd_UhEEpqC2ZoFCpGRzYzHK90ljsdpfTr
Content-Disposition: form-data; name="toto"
titi
--xjNHd_UhEEpqC2ZoFCpGRzYzHK90ljsdpfTr--
Connection: keep-alive
Content-Length: 135
Content-Type: multipart/form-data; boundary=xjNHd_UhEEpqC2ZoFCpGR
zYzHK90ljsdpfTr
Host: localhost:8081
User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_121)
Thanks for your help
Regards
Philippe M.
--
Cordialement.
Philippe Mouawad.
--
Cordialement.
Philippe Mouawad.
--
Cordialement.
Philippe Mouawad.
Gary Gregory
2017-06-03 19:10:16 UTC
Permalink
Post by Philippe Mouawad
Hello,
Any answers on those questions ?
Can you follow up with more detail perhaps on Oleg's reference to
https://www.ietf.org/rfc/rfc1341.txt ?

IOW, do you agree that the RFC allows for the HTTP message you posted?

Gary
Post by Philippe Mouawad
Thank you
On Sun, May 28, 2017 at 12:47 PM, Philippe Mouawad <
Post by Philippe Mouawad
Hi Oleg,
From the 3 questions I asked, to which one are you answering ?
The first ?
If possible, can you point the paragraph ?
Thanks
Post by Oleg Kalnichevski
Post by Philippe Mouawad
Hello,
Any thoughts on that ?
Hi Philippe
This is perfectly legal. See
https://www.ietf.org/rfc/rfc1341.txt
Oleg
Post by Philippe Mouawad
Thx
l.com>
Post by Philippe Mouawad
Hello,
Anybody has an idea about that ?
Thanks
On Mon, Apr 17, 2017 at 10:50 PM, Philippe Mouawad <
Post by Philippe Mouawad
Hello,
At JMeter we have a bug report (https://bz.apache.org/bugzill
a/show_bug.cgi?id=60800) related to Multipart Form POST request
A user reports that he has an issue with a request created by JMeter due
to the presence in Request Headers of "charset=US-ASCII" at end
of boundary
in Content-Type.
---------------------------------------------------------------
---------
POST http://localhost:8081/
--5v5So93EEOXPO8DIg4kmR-vfmsbimn
Content-Disposition: form-data; name="toto"
titi
--5v5So93EEOXPO8DIg4kmR-vfmsbimn--
*Request Headers:*
Connection: keep-alive
Content-Length: 123
*Content-Type: multipart/form-data;
boundary=5v5So93EEOXPO8DIg4kmR-vfmsbimn; charset=US-ASCII*
Host: localhost:8081
User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_121)
---------------------------------------------------------------
---------
The code is created through (https://github.com/apache/jme
ter/blob/trunk/src/protocol/http/org/apache/jmeter/
1/ MultipartEntityBuilder multipartEntityBuilder =
MultipartEntityBuilder.create();
multipartEntityBuilder.setCharset("US-ASCII");
3/
multipartEntityBuilder.setLaxMode();
StringBody stringBody = new
StringBody(arg.getValue(),
ContentType.create("text/plain", charset));
FormBodyPart formPart =
FormBodyPartBuilder.create(
parameterName, stringBody).build();
multipartEntityBuilder.addPart(formPart);
5/
HttpEntity entity = multipartEntityBuilder.build();
post.setEntity(entity);
1/ Is it correct to add this charset part ?
2/ Could you point me to the reference part of RFC that mentions this ?
3/ Is it correct to avoid setting charset in this case in API which would
lead to such request instead ?
POST http://localhost:8081/
--xjNHd_UhEEpqC2ZoFCpGRzYzHK90ljsdpfTr
Content-Disposition: form-data; name="toto"
titi
--xjNHd_UhEEpqC2ZoFCpGRzYzHK90ljsdpfTr--
Connection: keep-alive
Content-Length: 135
Content-Type: multipart/form-data; boundary=xjNHd_UhEEpqC2ZoFCpGR
zYzHK90ljsdpfTr
Host: localhost:8081
User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_121)
Thanks for your help
Regards
Philippe M.
--
Cordialement.
Philippe Mouawad.
--
Cordialement.
Philippe Mouawad.
--
Cordialement.
Philippe Mouawad.
Loading...