Repository navigation
application/json and gzip #787
Description
When a captured response has Content-Type: application/json and Content-Encoding: gzip it is encoded in Base64 in the simulation file.
Uncompressing this response to normal JSON text in the simulation file would enhance readability and understanding, make editing and versioning easier.
In simulate mode such a response could or should be compressed again to be closer to the actual API.
Reacted by Artem
Activity
JohnFDavenport commentedon Mar 1, 2019
Related to #815
GeorgeRadev commentedon Jun 9, 2020
Could there be an option for hoverctl export to decompress the gzip content ?
I agree that decompressing should be out of the proxy functionality,
and decompression is mostly needed when simulation is going to be edited for creating new simulations.
Thus, if export provide optional decompressing recordings it will be much easier to edit exported simulations and loading them after that.
Use JSON simulated GitHub responses, not gzip
Use JSON simulated GitHub responses, not gzip
Use JSON simulated GitHub responses, not gzip
Use JSON simulated GitHub responses, not gzip
Enable tests to run without a GitHub personal access token (#87)