Hi. I was thinking about creating an Enhancement request for this, but maybe it's worth discussing first.
HTTP Request Defaults currently has the following properties which aren't actually used anywhere: - Protocol (HTTP or HTTPS) - Method (GET or POST) - Path (actuall it CAN be used, but it's pretty useless) - Follow Redirects - Use KeepAlive It would be very convenient to be able to use the default value for the Protocol: in this way you could create and test a script on HTTP (which is easier to intercept by a Proxy, etc...) and then easily switch it to HTTPS. One way would be to convert this field into a select menu offering options HTTP and HTTPS on the Configuration element, plus a third option "Use default" on the HTTP Samplers. The Method is something which is specific to each request -- doesn't make much sense to define a default for it. I'd rather remove it from the HTTP Request Defaults element. The Path would be very easy to make useful (actually there was a request for this a few days ago in the user's list): just prepend it to any HTTPSampler path that doesn't start with a slash. I have my doubts on Follow Redirects, I guess it's pretty much like Method: not worth defining a default for it. Opinions? What about Use KeepAlive? Would it be useful to be able to define a default for it, so that you can switch it on and off for the whole script in a single shot? Salut, Jordi. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
