Releases: SpectoLabs/hoverfly
Releases · SpectoLabs/hoverfly
v0.6.0
Its time for a new minor version of Hoverfly.
Why have we gone from v0.5.17 to v0.6.0?
We made a slight change to the structure of payloads. We added a new field to indicate whether or not the body needs to be base64-encoded. The reason being that during the export and import process, any binary body data in a response would get lost due to being parsed to Unicode characters.
You can find out more about this change here. If you are trying to read or write binary data to the response body in your middleware, find out more here.
In this release, we have also introduced Ginkgo and Gomega to help us functionally test Hoverfly, which in turn has enabled us to start to modularize the codebase.
v0.5.17
Next version of UI and improved documentation
v0.5.16
v0.5.15
- BoltDB backend moved to separate package, currently used for requests/responses and metadata storage.
- Request body is now being minified before creating unique fingerprint ID to remove all spaces/new line symbols for JSON and XML content types.
- Destination can now be updated through API (restarts proxy goroutine)