jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <>
Subject Re: Hardcoded ISO-8859-1 ? [was: Start the next release 3.1 into 1-2 weeks?]
Date Mon, 19 Sep 2016 10:46:23 GMT
On 17 September 2016 at 14:39, harry_no_spot <> wrote:
>>Are you sure they are caused by JMeter?
> Sure they are caused by JMeter. There is an evidence.
> I only use the proxy function. With JMeter in some occasion the browser display junk
character, but meanwhile with Charles(another http proxy software) all is ok.
> So is it a simple but certain evidence?
> Pls refer to Bug 60070:
> I would like to suggest to review:
> 1. when jmeter as proxy. It encoded the request/POST as ISO-8859-1 crudely, and make
the sampler to access the destination server.

That seems to be what Bug 60070 is about.

> 2. when interpret HTTP header, jmeter only accept ASCII character, otherwize it will
throw Exception. but when the URL contains simplified chinese character?

What do you mean by this?
Can you provide an example?

> At 2016-09-13 22:51:32, "sebb" <> wrote:
>>On 13 September 2016 at 15:27, harry_no_spot <> wrote:
>>> I would like you guys to review the code,
>>> find all hard-corded encoding of 'ISO-8859-1'
>>> and give a way to deal this
>>> if u want people all round the world saying all different language can use this
>>> not only people using ur ISO-8859-1...
>>What problems have you found?
>>Are you sure they are caused by JMeter?
>>If so, please raise a sample bug report.
>>> At 2016-09-13 22:20:37, "Milamber" <> wrote:
>>>>Are you willing to start the next release process withing 1 to 2 weeks?
>>>>I can act as RM.
>>>>The next release will keep the Java 7 support (probably this release
>>>>will be the last with Java 7 support).
>>>>What are the bugs which will must be fixed before the next release?
>>>>If you want add an improvement before the next release, please indicate now.

View raw message