Hello Sebb, Thanks for the analysis. I agree with you and will try to handle these cases, do you prefer a discussion in mailing list or in issue ?
No problem for me if it is not taken into account in this release provided it is in next or not too far in the future so that patches are still valid :-) Regards Philippe On Wed, Sep 28, 2011 at 4:52 PM, sebb <seb...@gmail.com> wrote: > If HttpDefaults and HttpRequest both use Parameters, then the body is > created from both sets of parameters. > > When the body is being built, if any of the parameters have names, > only named parameters are kept. > Any unnamed parameters are ignored. > It's not possible to mix named and unnamed parameters; named > parameters take precedence. > > If both test elements have unnamed variables only, then the body is > created from the merging of the two sets of values. > > That is existing behaviour, and cannot be changed without potentially > affecting users. > > Now the raw body option is currently handled as an un-named parameter. > This means that the a Raw HTTP Request will be ignored if there is a > named default parameter, and unnamed default parameters will be > appended to the body. > > That does not seem right; I would expect the raw option to provide the > complete body. > > This will mean a change to the way defaults are handled. > > I think this needs more discussion. > > It could take a while to resolve the issues and debug the code, so I > think it will have to wait for a later version of JMeter; I've held up > the current one long enough! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@jakarta.apache.org > For additional commands, e-mail: dev-h...@jakarta.apache.org > > -- Cordialement. Philippe Mouawad. Ubik-Ingénierie
