WALD param style of headder is not treated as a headder
When a WADL has a parameter for a request that is of style header it is treated as a normal parameter when it should be forced to be a header for the test request.
Forum Discussion
SmartBear_Suppo
Alumni
AlumniHi,
thanks.. I've fixed the upcoming build to not url-encode header parameters. Regarding the Base64-encoding of parameter values, you could try the following:
1) Define a property holding the value of the parameter (ie your password)
2) Set the parameter value to a script: ${=Base64.decode( context.expand( '#TestCase#Password' ))}
(this isn't entirely correct but you get the idea..)
Would that work?
regards!
/Ole
eviware.com
thanks.. I've fixed the upcoming build to not url-encode header parameters. Regarding the Base64-encoding of parameter values, you could try the following:
1) Define a property holding the value of the parameter (ie your password)
2) Set the parameter value to a script: ${=Base64.decode( context.expand( '#TestCase#Password' ))}
(this isn't entirely correct but you get the idea..)
Would that work?
regards!
/Ole
eviware.com