You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2022/01/21 20:49:10 UTC

[Bug 65834] New: UTF8 instead of ISO-8859-1 by default for sampleresult.default.encoding

https://bz.apache.org/bugzilla/show_bug.cgi?id=65834

            Bug ID: 65834
           Summary: UTF8 instead of ISO-8859-1 by default for
                    sampleresult.default.encoding
           Product: JMeter
           Version: 5.4.3
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTTP
          Assignee: issues@jmeter.apache.org
          Reporter: sebastian.boga@endava.com
  Target Milestone: JMETER_5.5

When a browser get response from server through HTTP protocol, all chars are
returned as UTF-8 encoded.

By default in jmeter.properties file, it is set for for
sampleresult.default.encoding=ISO-8859-1

It would be better to have set the sampleresult.default.encoding=UTF-8 by
default in jmeter.properties file to have HTTP Request behaving more closely to
the browser.

Where do this have impact?
When using RegEx to extract some part from response, for cases where we have
white spaces like   in HTML, we got some  character instead of space. We
had to update manually jmeter.properties file in order to be able to extract
the string we wanted.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 65834] UTF8 instead of ISO-8859-1 by default for sampleresult.default.encoding

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65834

Felix Schumacher <fe...@internetallee.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #1 from Felix Schumacher <fe...@internetallee.de> ---
I think such a change should be discussed on the users (or developers) mailing
list.

Changing it will affect all users and should be done with care. On the other
hand, I believe that modern browsers are switching to utf-8 as default and
therefore it would be a good move to follow (in the long run).

I wonder, if such a setting would be useful on a per plan basis?

-- 
You are receiving this mail because:
You are the assignee for the bug.