Encoding of variables used as part of URI

[Guest FNW]

Hello Support Team,

 

I am trying to test a load balancer that uses redirection to distribute incoming requests. Hence, I set up a simple variable that searches for the redirect URL in the meta refresh tag of the redirection page. Although this variable is set correctly, there is a tricky problem when using it as part of URI in following pages: It seems like WAPT (6.0) automatically performs an URL encoding of the string stored inside a variable when it is referenced in the URI field. In my case, the redirection URI (= content of the variable) would be a value like /ssp1/, /ssp2/ or /ssp3/. But when examining the log files, this value is converted to e.g. %2Fssp1%2F by WAPT before being sent to the server in a GET request which results in a 404 error.

Is there any way to prevent automatic URL encoding of variables when they get used as part of URI ? Or is there another workaround to store the value of a dynamic redirection URL and use it within further parts of a test scenario ?

 

Thank you very much for any help !

 

 

FNW

[sergei 0]

In WAPT 6.0 you can disable encoding for an entire profile only. In the next version of WAPT it will be possible to disable encoding for some parameters or variables. If you will give us a profile and a full log, we will try to find a workaround for you.

[Guest FNW]

Hello Sergei,

 

thanks for your answer and your offer to examine my problem in order to find a workaround. While further investigating this particular problem, I found a workaround myself by simply avoiding slashes inside variables being used as URI references (so no modification by WAPT takes place). Although this required some slight changes on my side, everything works without any hassle, now.

 

Thanks again for your efforts !

 

 

FNW