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 Gordon,
thanks! If you double-click the imported PUT method you should see that the Authorization parameter has been correctly initialized as a HEADER parameter, and when you send the request its value will be added as an HTTP Header instead of a standard Query parameter. Is this not the behavior you are getting?
Also, regarding the PLAIN parameters, these are currently ignored when sending.. is that ok for you or would you like them to be handled in another way? (as a standard query parameter maybe?)
regards!
/Ole
eviware.com
thanks! If you double-click the imported PUT method you should see that the Authorization parameter has been correctly initialized as a HEADER parameter, and when you send the request its value will be added as an HTTP Header instead of a standard Query parameter. Is this not the behavior you are getting?
Also, regarding the PLAIN parameters, these are currently ignored when sending.. is that ok for you or would you like them to be handled in another way? (as a standard query parameter maybe?)
regards!
/Ole
eviware.com