I've now checked too, and it appears that ? is in fact allowed in a query string - the string is terminated by # or end of line.
Did not have time last night to fix this, but I hope to continue again later. S. On 25/04/06, Bruno POMMEREL <[EMAIL PROTECTED]> wrote: > I've checked quickly in the spec and didn't find any evidence of that. I'd > rather think it's > invalid too nevertheless. However, it does exist and I have to cope with -- > JMeter handles > it nicely with the 'encode' option uncheched for the first parameter, but by > default the > recorder does encode all parameters. I wish I could turn this off... > > Bruno. > > ----- Original Message ----- > From: "sebb" <[EMAIL PROTECTED]> > To: "JMeter Users List" <[email protected]> > Sent: Tuesday, April 25, 2006 12:36 AM > Subject: Re: No parameter encoding in http proxy ? > > > >I don't understand - how can there be two question marks in a single URL? > > > > Surely that is invalid? > > > > S. > > On 24/04/06, Bruno POMMEREL <[EMAIL PROTECTED]> wrote: > >> The path does exist in the url. The pb comes with the second question mark > >> that > >> Jmeter encodes systematically in proxy mode, whereas it's possible to ask > >> not to > >> encode it afterwards in the http request settings. > >> > >> Rgds, > >> > >> Bruno. > >> > >> > >> ----- Original Message ----- > >> From: "sebb" <[EMAIL PROTECTED]> > >> To: "JMeter Users List" <[email protected]> > >> Sent: Monday, April 24, 2006 8:45 PM > >> Subject: Re: No parameter encoding in http proxy ? > >> > >> > >> > I've just noticed that the quoted GET: > >> > > >> > host:port?abc?arg1=val1&arg2=val2. > >> > > >> > does not have a path. > >> > > >> > Is this correct? Or is something missing? > >> > > >> > Perhaps this is why JMeter works for me and not for you. > >> > > >> > S. > >> > On 24/04/06, sebb <[EMAIL PROTECTED]> wrote: > >> >> I just tried recording from: > >> >> > >> >> http://jakarta.apache.org/jmeter/known_bugs.html > >> >> > >> >> it followed the BugZilla enhancements link with no problems. > >> >> > >> >> S. > >> >> On 24/04/06, sebb <[EMAIL PROTECTED]> wrote: > >> >> > Which version of JMeter? > >> >> > > >> >> > Does this also happen with the nightly build? > >> >> > There were some fixes applied for double-encoding problems. > >> >> > > >> >> > S. > >> >> > On 24/04/06, Bruno POMMEREL <[EMAIL PROTECTED]> wrote: > >> >> > > The test plan fails to record, because the http proxy rewrites the > >> >> > > urls and encodes their > >> >> > > parameters. When replaying, it also fails unless I toggle the > >> >> > > "encode" option for the first > >> >> > > parameter. The point is that, unfortunately, it prevents me from > >> >> > > recording further. I'd > >> >> > > appreciate to be able to instruct jmeter not to re-encode requests > >> >> > > when proxying... > >> >> > > > >> >> > > Bruno. > >> >> > > > >> >> > > ----- Original Message ----- > >> >> > > From: "sebb" <[EMAIL PROTECTED]> > >> >> > > To: "JMeter Users List" <[email protected]> > >> >> > > Sent: Monday, April 24, 2006 6:57 PM > >> >> > > Subject: Re: No parameter encoding in http proxy ? > >> >> > > > >> >> > > > >> >> > > > Are you saying that the test plan fails during recording, or does > >> >> > > > it > >> >> > > > only fail on replay? > >> >> > > > > >> >> > > > S. > >> >> > > > On 24/04/06, Bruno POMMEREL <[EMAIL PROTECTED]> wrote: > >> >> > > >> > >> >> > > >> Hi all, > >> >> > > >> > >> >> > > >> I have a problem capturing a test plan using the builtin http > >> >> > > >> proxy : > >> >> > > >> > >> >> > > >> One on the very first request is a GET that looks like : > >> >> > > >> host:port?abc?arg1=val1&arg2=val2. > >> >> > > >> > >> >> > > >> Jmeter sees the first arg as abc?arg1, and encodes it, which > >> >> > > >> breaks what the server > >> >> > > >> expects. So I get an error back, which prevents me from > >> >> > > >> capturing further exchanges. > >> >> > > >> When I replay the test plan, it works ok it I uncheck the > >> >> > > >> "Encode" option for the > >> >> > > >> parameter in the http request gui. But I couldn't grab the > >> >> > > >> whole scenario... > >> >> > > >> > >> >> > > >> Is there a workaround ? Something like a global option to unset > >> >> > > >> encoding by default ? > >> >> > > >> > >> >> > > >> Tx for your help, > >> >> > > >> > >> >> > > >> Bruno. > >> >> > > >> > >> >> > > >> > >> >> > > >> > >> >> > > >> --------------------------------------------------------------------- > >> >> > > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> >> > > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> >> > > >> > >> >> > > >> > >> >> > > > > >> >> > > > --------------------------------------------------------------------- > >> >> > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > >> >> > > > For additional commands, e-mail: [EMAIL PROTECTED] > >> >> > > > > >> >> > > > > >> >> > > > >> >> > > > >> >> > > > >> >> > > --------------------------------------------------------------------- > >> >> > > To unsubscribe, e-mail: [EMAIL PROTECTED] > >> >> > > For additional commands, e-mail: [EMAIL PROTECTED] > >> >> > > > >> >> > > > >> >> > > >> >> > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: [EMAIL PROTECTED] > >> > For additional commands, e-mail: [EMAIL PROTECTED] > >> > > >> > > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
