Thank you for the kind words. >In JMeter 5.6.1 (a patch version) the default encoding for http samplers has been changed from the OS default one to UTF-8. Here is the pr: https://github.com/apache/jmeter/pull/6010
Sorry if it sounds like a dumb question, but could you please clarify what exact issue you have? For instance: "while doing X I expect Y but get Z". The change in PR6010 was mostly for "filenames" and "parameter names". It almost never makes sense in using "local encoding" for "file name", especially when standards say the default should be UTF-8. For instance, here's the sample: https://github.com/apache/jmeter/pull/6010/files#diff-f4ed3a459e14e38c22c8567f45dfb56a0f9844cb10d8e9ba8eaa3536c7859600L935 Previously, JMeter sent the file as "?_param", and after the change it improves to "安_param" Of course, you might consider "bug fixed" as "breakage of the backward compatibility", however, well, we need to fix bugs eventually. --- As a side note, there was JEP 400: UTF-8 by Default in Java 18+, see https://openjdk.org/jeps/400 That means, modern Java uses UTF-8 instead of "platform default" encoding. > I hope I can help in some other way than reporting issues not in the best time (before the release is done). Even though issues after the release might look as "not in the best time", as we can never have 100% test coverage. It does help when somebody tests the released versions. Vladimir
