andreaslind01 commented on PR #6742: URL: https://github.com/apache/jmeter/pull/6742#issuecomment-5276570051
Thanks for the detailed feedback and for laying out the use case so clearly. I agree that removing the field entirely would sacrifice a legitimate and valuable load-testing capability, particularly for side-by-side protocol comparisons within a single test plan. I've implemented the proposed direction and the changes are now available: * The **HTTP Version** field has been retained. * The available options are now **implementation-aware** and dynamically updated based on the selected HTTP implementation, preventing unsupported combinations from being selected. * `HttpClient4`, `Java`, and `HttpClient5` each expose only the protocol modes that are actually supported by their underlying implementation. * Support for **HTTP/2 Strict** has been added for `HttpClient5`, mapping to `FORCE_HTTP_2` independently of the scheme, while preserving the existing behavior of legacy `HTTP/2` configurations for backward compatibility. This keeps per-sampler protocol control available while eliminating the previous silent no-op combinations that motivated the original discussion. Thanks again for the suggestion. I think this results in a clearer UI without reducing functionality. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
