https://bz.apache.org/bugzilla/show_bug.cgi?id=63418
Bug ID: 63418
Summary: Recording: When recording records URL encoded values,
it should try to url decode them
Product: JMeter
Version: 5.1.1
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P2
Component: HTTP
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: JMETER_5.1.1
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
--
You are receiving this mail because:
You are the assignee for the bug.
