| || |
- 1 Post By jpulley3
VIEWSTATE Conversion Question
I am using LR v12.01 Build 2079 to develop some scripts for an ASP.NET application. I have been through the LoadRunner standard training course (couple times actually) but will admit it has been awhile.
I am running into an issue that I believe is related to VIEWSTATE correlation. Actually I think it's related to the conversion of the value.
The value at recording is /wEPDwUKMTc1MjY0NDg3Mg9kFgICAQ9kFgJmDxYCHgRUZXh0BQ1 SZWxlYXNlIDcuNS4==
The value sent from my web_submit_data is %2FwEPDwUKMTc1MjY0NDg3Mg9kFgICAQ9kFgJmDxYCHgRUZXh0 BQ1SZWxlYXNlIDcuNS4%3D%3D
I am capturing this value from the response of a prior request and then converting using this:
Which from my review of posts in searching for a solution to my problem is required when subsequently submitting a captured viewstate.
The value submitted (or converted) is %252FwEPDwUKMTc1MjY0NDg3Mg9kFgICAQ9kFgJmDxYCHgRUZX h0BQ1SZWxlYXNlIDcuNS4%253D%253D
When running with the viewstate value hard-coded in my request there are a couple redirections that occur from the primary. When I run the correlated/converted value I get a 200 response from the primary, but absolutely no body and no redirections either.
My first question would be am I correct in assuming this is as a result of the difference in the values of the viewstate? My second would be why is the "/" converting to %252F instead of %2F and the "=" converting to %253D instead of %3D? Am I doing something wrong with the web_convert_param and/or how do I get it to convert to what the original value is?
If anyone can school me here it would be very much appreciated.
It looks like you are starting with a "%2F" before the conversion, so the percent symbol is getting converted as a '%25.' in short, you appear to already be URL encoded in your response and you are re-encoding an already encoded URL response.
Reference: HTML URL Encoding Reference
You can use the sample URL encoder at the top of the reference and type in %2F, an already URL encoded value, and then hit URL encode and watch as it becomes '%252F,' which is representative of the issue you are observing.
Replace ineffective offshore contracts, LoadRunnerByTheHour
. Starting @ $19.95/hr USD.
Put us to the test, skilled expertise is less expensive than you might imagine.
Twitter: @LoadRunnerBTH @PerfBytes
Thanks for the reply James. As I have found on most occasions you are correct.
I saw in another post while researching my issue the need to convert the string before reuse and was not taking into account that the particular function I was using converted it on submission.