Hmmm... you're right. I always use the Proxy to create my scripts, so I'm probably too biassed towards this way of working, where longer writing doesn't matter. We should think about people who prefer (or have to) create their scripts by hand, too...
Instead, I will change the SOAP/XML sampler to ask for the URL component fields instead of a single URL as it does now.
This raises another issue, but I'll write about that in a separate e-mail.
Salut,
Jordi.
Michal Kostrzewa wrote:
change the HttpSampler so that it uses a URL as a single string instead of the current 4 component bits (protocol+domain+port+path).This would fix this bug#14533 as well as bug#12161 ("more Http Defaults options") and bug#13948 ("HTTP Request does not inherit from Port Number in HTTP Request Default"). Actually, it would probably make the whole Http Defaults config. element obsolete.
Hello,
Couple of thoughts and questions regarding that:
How we can live without HttpDefaults config element ? :-)) What if somebody wants to change a domain for example? Must he change every path in his scenario? Let's assume he uses a variable ${main_url}. Must he enter this ${main_url} string in every url in scenario?
OK, let's assume there is httpsDefaults config and he enter here his protocol://host:port/path. How he can enter urls in requests - full url (protocol://host:port/path) or only path part? If only path part - he can enter a relative path as well as full path (so there is a need for carefully merging paths). What if he wants to temporary change port - must he reenter the whole url? If he has a variable ${main_url} he can't just split it, exchange port and collect it again - he will have to rewrite all the url overriding and ignoring ${main_url}
best regards
Michal Kostrzewa
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
