https://bz.apache.org/bugzilla/show_bug.cgi?id=60120
--- Comment #9 from Stuart Barlow <[email protected]> --- Hi Philippe, Just revisiting this ticket after a lengthy pause. In the example I provided, the POST parameter value contains jumble of letters, digits and special characters. I'm not sure it is up to the application to decode. If this value was for example, a password and just happened to contain the sequence of characters %40 (or any other sequence that looks like an encoded character), if the application were to decode the value, the original value would be lost. The passwords would not match. We can agree that the specs are not clear, at least I haven't found a clear definition, but at the same time from the end-user's perspective, when using JMeter, if they see a check box that gives them the option to encode a parameter or not, they would expect toggling that check box to affect the behaviour. They would still expect JMeter to encode or not to encode. What do you think? -- You are receiving this mail because: You are the assignee for the bug.
