Re: [VOTE] Release JMeter 5.6.1 RC1

2023-06-30 Thread Vladimir Sitnikov
There's a question on displaying default values in UI: https://github.com/apache/jmeter/issues/6026 They say it is confusing to see the defaults in "HTTP Request Defaults" since the user can't tell if it will overwrite HTTP request or not. I agree it is confusing, and it brings a new question:

[GitHub] [jmeter] koudela5 commented on issue #6026: HTTP Request sampler displays default values in some fields

2023-06-30 Thread via GitHub
koudela5 commented on issue #6026: URL: https://github.com/apache/jmeter/issues/6026#issuecomment-1614559476 That's good question. You cannot distinguish between false and default state. I would leave the bevaviour as it was in version 5.5 and below for now. What about using a tri-state

[GitHub] [jmeter] vlsi commented on issue #6026: HTTP Request sampler displays default values in some fields

2023-06-30 Thread via GitHub
vlsi commented on issue #6026: URL: https://github.com/apache/jmeter/issues/6026#issuecomment-1614520251 Just wondering what would you say about checkboxes? For instance, open "HTTP Request Defaults", switch to "Advanced" tab, and try to guess if `[ ] Save response as MD5 hash?`

[GitHub] [jmeter] koudela5 commented on issue #6026: HTTP Request sampler displays default values in some fields

2023-06-30 Thread via GitHub
koudela5 commented on issue #6026: URL: https://github.com/apache/jmeter/issues/6026#issuecomment-1614492052 It is very confusing especially along with HTTP Request Defaults, see following: ![image](https://github.com/apache/jmeter/assets/113984709/7bd35442-01c5-4acd-b0e1-733e02c7053f)

[GitHub] [jmeter] koudela5 opened a new issue, #6026: HTTP Request sampler displays default values in some fields

2023-06-30 Thread via GitHub
koudela5 opened a new issue, #6026: URL: https://github.com/apache/jmeter/issues/6026 ### Expected behavior Protocol and Content encoding fields in HTTP Request sampler should display empty value in GUI by default.

[GitHub] [jmeter] vlsi opened a new issue, #6025: Implement "strict mode" where referencing an undefined variable in ${nonExistingVar} would fail

2023-06-30 Thread via GitHub
vlsi opened a new issue, #6025: URL: https://github.com/apache/jmeter/issues/6025 ### Use case Currently, a typo in variable name is hard to spot as it might silently pass to the downstream system unnoticed. ### Possible solution It might be helpful if we implement

[GitHub] [jmeter] bpradipta6 commented on issue #5999: JMeter 5.5 + Linux machine execution with inputs as client certificate ( pkc12) with password - not working

2023-06-30 Thread via GitHub
bpradipta6 commented on issue #5999: URL: https://github.com/apache/jmeter/issues/5999#issuecomment-1614287921 #javax.net.ssl.keyStoreType=pkcs12 (or jks) javax.net.ssl.keyStore=/root/apache-jmeter-5.5/ javax.net.ssl.keyStorePassword= -- This is an automated message from

[GitHub] [jmeter] vlsi commented on issue #5999: JMeter 5.5 + Linux machine execution with inputs as client certificate ( pkc12) with password - not working

2023-06-30 Thread via GitHub
vlsi commented on issue #5999: URL: https://github.com/apache/jmeter/issues/5999#issuecomment-1614273859 Pull requests to improve the feature and the documentation are welcome. The current code uses java properties, so it is hard to tell what goes wrong in your case without a

[GitHub] [jmeter] bpradipta6 commented on issue #5999: JMeter 5.5 + Linux machine execution with inputs as client certificate ( pkc12) with password - not working

2023-06-30 Thread via GitHub
bpradipta6 commented on issue #5999: URL: https://github.com/apache/jmeter/issues/5999#issuecomment-1614265599 Hi @vlsi Thanks for the update. But I have used Java properties Not the JMeter properties. but still it's not working. Can't attached the screen shot due to client