GZIP encoding and UserPath recording

Hello ​@miroslav.trandafilovic ,

Yes, recording a User Path on a platform using GZIP encoding in NeoLoad is definitely possible. The issue of unreadable binary data you’re encountering is due to the requests and responses being compressed. Here's how you can resolve this:

1. Enable Automatic GZIP Decompression in NeoLoad

NeoLoad has the capability to automatically decompress GZIP-encoded content during the recording process. To activate this feature:

1. Open NeoLoad.
2. Navigate to Preferences > Proxy.
3. Make sure the option "Decode GZIP-encoded content during recording" is checked.
4. Start your recording again to see if the content is now properly readable.

2. Configure Custom Headers

In some cases, the server compresses content based on the Accept-Encoding header sent by the client. To override this behavior during recording:

1. Go to Edit > Recording Settings > Advanced in NeoLoad.
2. Modify or remove the Accept-Encoding header to prevent the request from asking for compressed content.
   • For example, change Accept-Encoding:gzip to Accept-Encoding: identity.

3. Post-Recording Decoding

If you still encounter GZIP-compressed content after recording:

1. Review the recorded requests and responses that contain unreadable binary data.
2. Use NeoLoad’s Variable Extractors or external tools, such as Python scripts or browser developer tools, to decode and read the content.

4. Server-Side Adjustments (If Possible)

If you have control over the server being tested, consider temporarily disabling GZIP compression in your test environment. This will allow NeoLoad to capture plain-text data during recording.

5. Verify Compression During Replay

To ensure that the GZIP behavior is correctly maintained during test execution:

1. Check the headers in your User Path during the validation phase to confirm that NeoLoad is sending the correct Accept-Encoding header.
2. NeoLoad should by default send the same header as captured during recording, so the compression should be properly handled.

By following these methods, you should be able to manage GZIP-encoded requests and responses effectively when recording a User Path in NeoLoad. Feel free to reach out if you need further clarification!

Thanks,

Ramanan

Hello ​@miroslav.trandafilovic ,

Kindly confirm here is your issue resolved?

Thanks,

Ramanan