Using a ${var} for the HTTP protocol?

[Jordi Salvat i Alabart]

Hi.

Another idea for consideration (stemming from my recent discussion on entering URLs as a single string).

Problem:

I've frequently found myself writing (or recording) scripts which use both http and https, then using them on different environments (development, QA, production), some of which have https set-up, others don't. Currently, changing the script back and forth between using mixed http and https is a pain, since it requires going through the whole script and changing all affected samplers. (There's an alternate solution using the HttpDefaults in a perverted way, but anyway it doesn't work if there's two URLs that need to be changed between HTTP and HTTPS independently -- less frequent, but still happened to me).

The solution would be to use a ${var} for the protocol field, but that is not currently possible, since that field is entered using a couple of radio buttons.

Proposed solution A:

Enter the protocol field as text.

Drawbacks: more writing, possibly less obvious usage than the current radio buttons.

Proposed solution B:

Have an "other" radio button besides "HTTP" and "HTTPS", and a text field which will only be enabled if "other" is chosen.

Drawbacks: more complex implementation, more screen real-state used.

If we chose B, we would also need to decide which mechanism to use to select the default given in the HTTP Defaults config element:

Ba/ yet another radio button labelled "Default", or
Bb/ choose "other" and leave the text field blank

Opinions?

Salut,

Jordi.


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>