I am load testing a REST service that requires a basic authentication authorization header.
When I set a HTTP Header, in the Request itself or in the Profile Defaults, it is removed from the request that is made.
Request Headers
Accept-Language : en-GB
Accept-Tenant : uk
Authorization : Basic aVBob25lLVYxOmVjNjhlNTY3NjU4NGRkN2ZiZjMxN2IzOWY0M2VmNWY1MDJhMjljNzc=
Accept-Charset : utf-8
Host : http://xxxxx-labs.com
User-Agent: perftesting
Content-Type : application/json
It also appears to be stripping out the Content-Type Header.
This worked fine in 2.0 but we have now upgraded to 3.0 and are seeing the above behaviour.
Logs from Wapt Console
<% 00:00:00.000(08:41:14.551) REQUEST_HEADER %>
[% CONTENT 263 %]
GET /books?q=n1 HTTP/1.0
Accept-Language: en-GB
Accept-Tenant: uk
Accept-Charset: utf-8
User-Agent: perftesting
Host: http://xxxxx-labs.com
<% 00:00:00.000(08:41:14.551) RESPONSE_FAILED %>
[% CONTENT 252 %]
HTTP/1.1 400 Bad Request
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Wed, 20 Feb 2013 08:41:14 GMT
Server: Microsoft-IIS/7.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Content-Length: 97
Connection: Close
<% 00:00:00.000(08:41:14.551) RESPONSE_BODY %>
[% CONTENT 97 %]
{"Errors":[{"ErrorType":"Error","Message":"Authorization header is not valid"}],"HasErrors":true}
