I found this in an internal note here at BMC:
If the error "HTTP: 1000 - invalid header, receive response failed" occurs during a Try-Script in TM ART it usually means that the response issued by the server is not adhering to HTTP specifications. The TM ART Replay Engine adheres strictly to HTTP 1.0 and 1.1 specification; therefore if a server response is invalid, TM ART will close the connection and retry the client request. If the subsequent server response for the second client request fails then the error will be thrown in TM ART and the request will have failed.
One recent example of this error was caused by a Server sending two spaces before the "HTTP 1.1" header in the server response, like so:
**HTTP 1.1 200 OK
[Where * indicates a white space]
The above is an invalid HTTP response because of the two spaces which prefixed the HTTP header. The problem with the server response was highlighted by using a Network Sniff tool to view the network traffic between the Client and Server. You can download a Network Sniff tool from the Ethereal Site
You could also consider this solution from the knowledge base:
Go to settings --> active profile --> record --> internet --> security with ssl version to "automatic" and encryption strength to "128 bit encryption" and then the client and server should handshake successfully.
I've had to do the same but changing strength to "Triple DES". I've started to just include this line in the bdl:
Thanks for your help.
I changed the security values but the problem continues.
Hello Lilian, Have you resolved this issue?
If not - Did you analyzed the test using the TrueLog Explorer to see how the replay header differs from the original recording?
Sometimes, a Unique session ID needs to be captured and submitted in order to get a valid response from the target server.