12-20-2011 09:02 AM - edited 12-20-2011 09:11 AM
We are having an issue getting the HP LoadRunner to properly record SOAP messages that are compressed with either DEFLATE or GZIP compression. Any suggestions? Example message format? Any special header attribute that LoadRunner is looking for?
I would be happy to explain in more detail. Since i do not know or configure LoadRunner, I do not know what information is needed to troubleshoot the problem. If you are willing to help, I would be happy to provide as much additional information needed to figure this out.
Steps that our application goes through for compression. (Clients do these steps in reverse)
1. Take contents of Body tag and compress it using deflate.
2. Base64 encode the comrpessed content
3. Write the CompressedBody tag with the Base64 + compressed content inside
<s:Envelope xmlns:s=\"http://schemas.xmlsoap.org/soap/envelope/\"><s:Body><CompressedBody xmlns=\"urn:wcfextensions:soap:compression\">7b0HY
12-21-2011 11:41 AM
I have a similar problem, I recorded mine user a sniffer, but my message body comes as cQATbDiHYTuwTFhHqZsr9sAp4vVjupvsWOb8Pig3SgrBmgsn0p
01-03-2012 05:38 AM
Using the DFE feature (which is already released with LoadRunner) you can write a DFE that will encode/decode the compression
for a future release we are working on a new API for decompressing...