Bug 63418 - Recording: When recording records URL encoded values, it should try to url decode them
Summary: Recording: When recording records URL encoded values, it should try to url de...
Status: NEW
Alias: None
Product: JMeter
Classification: Unclassified
Component: HTTP (show other bugs)
Version: 5.1.1
Hardware: All All
: P2 enhancement (vote)
Target Milestone: JMETER_5.1.1
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-10 01:20 UTC by Philippe Mouawad
Modified: 2019-05-10 01:20 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
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