DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=27480>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27480 Can't use CSVRead in HTTP Request Defaults - problem with 'next' actually [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Can't use CSVRead in HTTP |Can't use CSVRead in HTTP |Request Defaults |Request Defaults - problem | |with 'next' actually ------- Additional Comments From [EMAIL PROTECTED] 2004-03-08 21:10 ------- Sebb, I have narrowed down the problem and have attached a test case that should duplicate it. I'm using the 02/24 nightly build but I've seen this issue with 1.9.1 and 02/07 builds as well. Each of the HTTP Request Default's (Protocol, Server Name and Port) look like this: ${__CSVRead(${ThreadConfig},0)}${__CSVRead(${ThreadConfig},next)} It's the 'next' that the problem; and if I remove it and place the protocol, IP and port on the same row it works. If you run as is, you'll notice the malformed URLs in the request tab of the tree listener. As you can see from my CSV file, the goal was to place the settings for a single environment in a column and use a variable for the index; that way one change would allow me to switch environments. I'll look into ${__p()} as you can suggest; I don't yet know what it does yet but I can read about it. thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
