Bug 63418

Summary: Recording: When recording records URL encoded values, it should try to url decode them
Product: JMeter - Now in Github Reporter: Philippe Mouawad <p.mouawad>
Component: HTTPAssignee: JMeter issues mailing list <issues>
Status: NEW ---    
Severity: enhancement    
Priority: P2    
Version: 5.1.1   
Target Milestone: JMETER_5.1.1   
Hardware: All   
OS: All   

Description Philippe Mouawad 2019-05-10 01:20:43 UTC 
Not sure it's the right solution but creating a bug to write this.

Currently when you have a token to correlate that contains character requiring URL encoding, HTTP Request will be created with URL encoded values while the pages in recording can have initial values not URL encoded.
If you try to find IDs you won't be able to because of the comparison failure.


2 options:

- Either try to URL decode in requests created, but that might introduce issue
- Make Search feature smarter by trying to make it compare both URL encoded and non encoded value
Comment 1 The ASF infrastructure team 2022-09-24 20:38:16 UTC 
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/5064