Hello,
We have a bug report at JMeter :
https://bz.apache.org/bugzilla/show_bug.cgi?id=60120
Where a user post a form with a parameter having this value
'IqGo6EM1JEVZ+MSRJqUSo@qhjVMSFBTs'
It appears that the '@' character is encoded.
The form is submitted using application/x-www-form-urlencoded
On Sat, 2016-09-17 at 15:55 +0200, Philippe Mouawad wrote:
> Hello,
> We have a bug report at JMeter :
> https://bz.apache.org/bugzilla/show_bug.cgi?id=60120
>
> Where a user post a form with a parameter having this value
> 'IqGo6EM1JEVZ+MSRJqUSo@qhjVMSFBTs'
>
> It appears that the '@' character
On Sunday, September 18, 2016, Oleg Kalnichevski wrote:
> On Sat, 2016-09-17 at 15:55 +0200, Philippe Mouawad wrote:
> > Hello,
> > We have a bug report at JMeter :
> > https://bz.apache.org/bugzilla/show_bug.cgi?id=60120
> >
> > Where a user post a form with a parameter having this value
> > 'I
On Sun, 2016-09-18 at 14:08 +0200, Philippe Mouawad wrote:
> On Sunday, September 18, 2016, Oleg Kalnichevski wrote:
>
> > On Sat, 2016-09-17 at 15:55 +0200, Philippe Mouawad wrote:
> > > Hello,
> > > We have a bug report at JMeter :
> > > https://bz.apache.org/bugzilla/show_bug.cgi?id=60120
> >
Hi Oleg,
Thanks for rapid answer.
Correct me if I am wrong but:
- URLENCODER is built from an or on UNRESERVED (which contains '_', '-',
'.', '*' and a-z, A-Z, 0-9.
URLENCODER is passed as safechars in
private static String urlEncode(
final String content,
final Charset
On Sun, 2016-09-18 at 15:11 +0200, Philippe Mouawad wrote:
> Hi Oleg,
> Thanks for rapid answer.
> Correct me if I am wrong but:
> - URLENCODER is built from an or on UNRESERVED (which contains '_', '-',
> '.', '*' and a-z, A-Z, 0-9.
>
> URLENCODER is passed as safechars in
> private static St
So is it a bug ? or a regular behaviour ?
thanks
On Sunday, September 18, 2016, Oleg Kalnichevski wrote:
> On Sun, 2016-09-18 at 15:11 +0200, Philippe Mouawad wrote:
> > Hi Oleg,
> > Thanks for rapid answer.
> > Correct me if I am wrong but:
> > - URLENCODER is built from an or on UNRESERVED (w
On Sun, 2016-09-18 at 16:12 +0200, Philippe Mouawad wrote:
> So is it a bug ? or a regular behaviour ?
>
We back to where we started. Why do you think it should not be encoded?
Oleg
> thanks
>
> On Sunday, September 18, 2016, Oleg Kalnichevski wrote:
>
> > On Sun, 2016-09-18 at 15:11 +0200,
On Sunday, September 18, 2016, Oleg Kalnichevski wrote:
> On Sun, 2016-09-18 at 16:12 +0200, Philippe Mouawad wrote:
> > So is it a bug ? or a regular behaviour ?
> >
>
> We back to where we started. Why do you think it should not be encoded?
it does not seem to be when using browser.
It should
Hello,
While I think it does not hurt to encode it, if you look at the context (form
represrntation) you only need to escape characters which hinder thenparsing of
forms. And @ is not a problem for that
Gruss
Bernd
--
http://bernd.eckenfels.net
>From Win 10 Mobile
Von: Oleg Kalnichevski
On Sun, 2016-09-18 at 16:27 +0200, Philippe Mouawad wrote:
> On Sunday, September 18, 2016, Oleg Kalnichevski wrote:
>
> > On Sun, 2016-09-18 at 16:12 +0200, Philippe Mouawad wrote:
> > > So is it a bug ? or a regular behaviour ?
> > >
> >
> > We back to where we started. Why do you think it shou
Hi Oleg,
If you look at :
https://bz.apache.org/bugzilla/show_bug.cgi?id=60120
You can see that this encoding can break some applications.
If I read https://en.wikipedia.org/wiki/Percent-encoding#The_
application.2Fx-www-form-urlencoded_type
Which references https://tools.ietf.org/html/rfc1630
I
On Sat, 2016-09-24 at 10:50 +0200, Philippe Mouawad wrote:
> Hi Oleg,
> If you look at :
> https://bz.apache.org/bugzilla/show_bug.cgi?id=60120
> You can see that this encoding can break some applications.
>
> If I read https://en.wikipedia.org/wiki/Percent-encoding#The_
> application.2Fx-www-form
13 matches
Mail list logo