DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12161>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12161 more Http Defaults options ------- Additional Comments From [EMAIL PROTECTED] 2002-08-30 02:22 ------- I would like to propose extend the scope of this enhancement request. I am parameterising my JMeter test plans and also trying to create reusable or 'stock template' sub-groups of requests (each sub-group is a set of config elements and samplers collected by a Simple Controller). I can add an HTTP Defaults config element to a sub-group and use it to make the sub-group use HTTPS instead of HTTP, using this enhancement as it is currently stated. That's great! I can also set the port in the HTTP Defaults config element too, so I can set up each sub-group to use http on port a or https on port b. Now, how can I get 'preferences' or 'parameters' global to the Test Plan to affect all the sub-groups? Or affect all the sub-groups I want to call 'secure' accesses (leaving the others as 'insecure')? I can add to the Test Plan the user variable 'httpsPort', and give it the value of the port, b. Through all my HTTP Default config elements in the plan, for those config elements controlling sub-groups representing 'secure' accesses, I just use Port: ${httpsPort}. So, when I want to run my test plan against a plain HTTP installation of my app, I can just change httpsPort to the value 'a' and get plain HTTP test going! But that's not sufficient. I have to visit each HTTP Defaults config element in each 'secure' sub-group and also switch the radio button to HTTP. It would be very nice be able to control both the protocol (http/s) and the port by simple changing a pair (or a single) user variable value at the top of the test plan. This requires that the protocol not be set by a radio button selection, but by a text field (perhaps with constraints on its value), and the text field be able to use ${var} for its value. ${var} must of course expand to a valid protocol string. How to work this all in to this enhancement, or whether to deal with it as a separate enhancement, is up to the JMeter dev team. Thanks for your efforts. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
