I order to do manual correlation you have to understand and parse response content or post data. The data is typically unreadable, here's a real life example:
Cookie: securityToken=%7B%22serviceDeskEmail%22%3A%22john.doe%40noone.biz%22%2C%22showRulesFired%22%3A%22true%22%2C%22userName%22%3A%22JOHN%22%2C%22env%22%3A%22TEST%22%2C%22vbmsCoreContextPdfViewer%22%3Anull%2C%22version%22%3A%221.2.0-924%22%2C%22hostViaJava%22%3A%22localhost%22%2C%22authorities%22%3A%5B%7B%22authority%22%3A%22ROLE_WEBAPP%22%7D%2C%7B%22authority%22%3A%22JOHN%22%7D%2C%7B%22authority%22%3A%22Case%20Manager%22%7D%2C%7B%22authority%22%3A%22Search%20Letters%22%7D%2C%7B%22authority%22%3A%22Edit%20Profile%20Information%22%7D%2C%7B%22authority%22%3A%22Read%20Reject%20Reasons%22%7D%2C%7B%22authority%22%3A%22Edit%20Letter%22%7D%2C%7B%22authority%22%3A%22View%20Left%20Flyout%22%7D%2C%7B%22authority%22%3A%22Preview%2FPrint%20Letters%22%7D%2C%7B%22authority%22%3A%22Manage%20Letter%20Templates%20-%20View%22%7D%2C%7B%22authority%22%3A%22View%20Right%20Flyout%22%7D%2C%7B%22authority%22%3A%22Run%20Reports%22%7D%2C%7B%22authority%22%3A%22User%20Dashboard%22%7D%2C%7B%22authority%22%3A%22Edit%20Letter%20Details%22%7D%2C%7B%22authority%22%3A%22View%20Dashboard%22%7D%2C%7B%22authority%22%3A%22Delete%20Letter%22%7D%2C%7B%22authority%22%3A%22View%20No%20LetterHeads%22%7D%5D%2C%22node%22%3A%22localhost8%22%2C%22attachmentMaxSize%22%3A%2250000000%22%2C%22ssoLogoutURL%22%3Anull%2C%22vbmsURL%22%3Anull%2C%22serviceDeskInfo%22%3A%22%20TODO%3A%20Setup%20ServiceDesk%20Program%22%2C%22locationId%22%3A%22317%22%2C%22showExceptionsToUser%22%3Atrue%2C%22success%22%3Atrue%2C%22host%22%3A%22localhost%22%2C%22mainWebappUrl%22%3A%22%2Fmel%2Fwebapp%2Fsecure%2Fstart%22%2C%22contextHelpURL%22%3A%22%22%7D;
No one can read that.
So I use online tools (see this blog posting at https://www.ibm.com/developerworks/community/blogs/nfrsblog/entry/Using_various_on_line_tools_to_parse_POST_and_response_content_in_Rational_Performance_Tester?lang=en) to URL decode, split string, format XML or JSON.
I have to go through multiple on line tools, eventually I get something I can look at
Cookie: securityToken={"serviceDeskEmail":"john.doe@noone.biz"
"showRulesFired":"true"
"userName":"JOHN"
"env":"TEST"
"vbmsCoreContextPdfViewer":null
"version":"1.2.0-924"
"hostViaJava":"localhost"
"authorities":[{"authority":"ROLE_WEBAPP"}
{"authority":"JOHN"}
{"authority":"Case Manager"}
{"authority":"Search Letters"}
{"authority":"Edit Profile Information"}
{"authority":"Read Reject Reasons"}
{"authority":"Edit Letter"}
{"authority":"View Left Flyout"}
{"authority":"Preview/Print Letters"}
{"authority":"Manage Letter Templates - View"}
{"authority":"View Right Flyout"}
{"authority":"Run Reports"}
{"authority":"User Dashboard"}
{"authority":"Edit Letter Details"}
{"authority":"View Dashboard"}
{"authority":"Delete Letter"}
{"authority":"View No LetterHeads"}]
"node":"localhost8"
"attachmentMaxSize":"50000000"
"ssoLogoutURL":null
"vbmsURL":null
"serviceDeskInfo":" TODO: Setup ServiceDesk Program"
"locationId":"317"
"showExceptionsToUser":true
"success":true
"host":"localhost"
"mainWebappUrl":"/mel/webapp/secure/start"
"contextHelpURL":""};
The feature that is described in this request is a candidate for a future release.
Attachment (Description): text after splitting on ",". I would then paste this into ntoepad
Attachment (Description): decoded text copied to string split tool
Attachment (Description): text after being URL decoded
Attachment (Description): text copied from Request content to online URL decoder