https://bz.apache.org/bugzilla/show_bug.cgi?id=60120
Stuart Barlow <stuart.bar...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WORKSFORME |---
Status|RESOLVED |REOPENED
--- Comment #8 from Stuart Barlow <stuart.bar...@gmail.com> ---
Hi Philippe
I'm not sure a Wikipedia page can be used definitively but I found this
https://en.wikipedia.org/wiki/Percent-encoding#Percent-encoding_reserved_characters
"When a character from the reserved set (a "reserved character") has special
meaning (a "reserved purpose") in a certain context, and a URI scheme says that
it is necessary to use that character for some other purpose, then the
character must be percent-encoded."
I think the RFCs leave it open and optional. It depends on the context.
Likewise it should probably be optional for JMeter users too.
Thanks for looking into it and I see you've put effort in but I would still
disagree. I feel JMeter is defective. From the users' perspective, whether they
click the 'encode?' checkbox or not should influence whether that parameter is
percent-encoded or not. At the moment @ is encoded whether the check box is
clicked or not. The user isn't aware or concerned what underlying API is used.
Just because Java does it, doesn't mean it is right :)
Regards
--
You are receiving this mail because:
You are the assignee for the bug.
