v1.1.2

Thanks to @kulaginds' PR, you can now use templating functions in the response headers.

v1.1.1

Overwrite duplicate request in capture mode

Hoverfly by default ignores repeated requests when capturing. Using the following flag, you can set Hoverfly to capture the new request-response pair by overwriting the old one.

hoverctl mode capture --overwrite-duplicate

Bug fixes and performance improvements

Thanks to @aosavitski's PR, the performance of stateful simulation has been improved.
This release also fixed the following bugs:
#868
#865

v1.1.0

CORS support

You can now enable Cross-Origin Resource Sharing (CORS) support on hoverfly. Your web application running on the browser can make requests to Hoverfly even it’s not on the same domain.

hoverfly -cors

or

hoverctl start --cors

For more information, please see the docs.

Disable duplicate request check on simulation import

Some users experience slow import for large simulation file (a few hundred MBs with lots of pairs), you can speed it up by disabling the duplicate request checking feature:

hoverfly -no-import-check

or

hoverctl start --no-import-check

Custom Hoverfly response header

A response proxied by Hoverfly contains header Hoverfly: Was-Here. In this release, we are adding Hoverfly: Forwarded to it if a request is not simulated but forwarded to the remote service in SPY mode.

v1.0.1

A new helper method for response templating

We have added a new helper method for string find and replace:

{{ replace string oldValue newValue }}

For example, you can solve the problem in issue #841 with this templating function which replaces all occurrences of "_token" in the query params with an empty string.

{{ replace Request.QueryParam.access_token.[0] "_token" "" }}

Support multiple simulation imports through hoverctl

You can now import multiple simulations when you start hoverfly using hoverctl :

hoverctl start --import foo.json --import bar.json

This is equivalent to the following hoverfly command:

hoverfly -import foo.json -import bar.json

You can also add additional simulations after hoverfly is started:

hoverctl simulation add foo.json bar.json

Bug fixes

This release also fixes the following bugs:

• #839: Importing multiple simulations with stateful sequences should initialize all sequences
• #852: Import an existing simulation and re-capturing the same requests will no longer create duplications.

v1.0.0

After the previous two RC versions, we are so excited to finally release Hoverfly v1.0.0. We really appreciate all the contributions and feedback from the community!

Partial JSON matching

A big thanks to @dilitvinov, a new matcher (jsonPartial) is available to let you partially match a JSON document. You can find out more here here.

Simulate and capture HTTP response trailers

Some APIs use HTTP response trailers, and we have implemented a solution to capture them as normal headers:

"response" : {
    "headers" : {
           "Trailer": ["X-Streaming-Error"],
           "X-Streaming-Error" : [ "Connection Closed" ]
     }
}

Kubernetes deployment using Helm

Hoverfly Helm chart has been accepted into the official Helm incubator repository.

You can simply run the following command to deploy Hoverfly into your Kubernetes cluster:

helm install incubator/hoverfly

You can find more details in the doc.

Alpine based Docker image

Thanks to @rusenask, the Hoverfly v1.0.0 Docker image will be much slimmer as it based on Alpine, and the Dockerfile uses multi-stage build.

Bug fixes

• Thanks to @DanielJonesEB, we have fixed issues with using Go Modules and Hoverfly.
• Goproxy dependency version is rolled back as it has a dramatic impact on HTTPS MITM performance since the release of v1.0.0-rc.1.
• Fix security issues in Hoverfly UI.

v1.0.0-rc.2

Performance improvement

This release improves performance. These improvements will save both CPU time and reduce latency, in some cases by a significant margin. Thanks to the Hoverfly community for their assistance in identifying and fixing these issues.

• Hoverfly used to parse templates on every response whereas it now caches the parsed templates. Expect to see a significant improvement if your load tests contain large templated responses.
• The response body is now only read to check the content length when absolutely necessary.
• We have also introduced a fixed size LRU cache for request/response caching. Hoverfly no longer encodes and decodes the cached value saving a lot of CPU time.
• The request/response cache is now fixed to 1000 entries by default which should remove the possibility of the cache exceeding the available memory. Its value can be configured with the following flag:

 $ hoverfly -cache-size 100

Bug fix

Fixed an issue which prevented hoverctl controlling a remote hoverfly running in a Docker container: #801

v1.0.0-rc.1

Happy Friday! We are thrilled to announce an RC release of v1.0.0!

The v5 simulation schema introduced since v0.17.0 is stable and easy to extend for more powerful request matchers. It lays a good foundation for us to implement matcher chaining to solve XML/JSON matching issues without introducing breaking changes. That's when we start considering a Hoverfly v1 release.

Thank you for all your contributions, we are hoping to work with you again on more exciting features in the coming months, and make Hoverfly shines!

Adding delay based on Log-normal Distribution

Thanks to @podtserkovskiy's contribution, you can now enable random delay in a simulation based on log-normal distribution. Here is an example:

"globalActions": {
         "delaysLogNormal": [
            {
               "urlPattern": ".",
               "httpMethod": "",
               "min": 100,
               "max": 10000,
               "mean": 5000,
               "median": 500
            }
         ]
      }

where mean and median values could be calculated from your actual server response times, and Hoverfly generate random latencies that are lognormally distributed based on these parameters.

Controlling log level

Default log level of Hoverfly is info, but if you prefer less noise or a bit concern about the performance overheads of info logging, you can control the log level with this release:

$ hoverfly -log-level warn 

Which logs warning level or above (error, fatal and panic)

Bug fixes

Some long-standing bugs have been addressed in this release, such as bugs that affect multi-value query capture, config.yaml loading and plain HTTP tunnelling.

#704
#752
#786
#792

v0.17.7

This is a pure bugfix release to address the following issues:

Hoverfly crashed under heavy load in webserver mode

While we helped the community with load testing issues using hoverfly, we fixed a few bugs causing hoverfly to crash under load. This includes transistive bugs from an old version of logrus, concurrent read/write access to map, and usage counter failed to update in webserver mode(#776)

Query parameters were duplicated in the journal

This bug can be confusing when you need to debug an unmatched request. As reported by hoverfly-java users SpectoLabs/hoverfly-java#187, the query parameters are duplicated in the closest-match debug message.

v0.17.6

Two-way SSL authentication support

A huge thanks to @xiang-zhu's PR, Hoverfly finally has support for two-way SSL authentication. This new feature lets you capture or spy an HTTPS server that requires this authentication method. You can provide certificate key, client certificate and CA certificate with the following flags when starting hoverfly:

--client-authentication-client-key
--client-authentication-client-cert
--client-authentication-ca-cert

You must also provide a host pattern using --client-authentication-destination flag to tell Hoverfly which request hosts should be called using this authentication method.

Bug fix to capturing concurrent requests with state

Thanks again to @john4744 for fixing a concurrency issue when doing stateful capture. Hoverfly should now generate the correct state values when capturing concurrent requests.

v0.17.5

Bug fix to simulating concurrent requests with state

Thanks again to @john4744 for spotting and fixing a bug in the state part of Hoverfly. Hoverfly did not use any locks on the state, meaning there could be concurrency issues with multiple requests and responses using and modifying state.

Bug fix to simulation import warnings

A bug was noticed regarding warnings when importing simulations with Content-Length headers on the responses with encoded bodies. This has now been fixed.