GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Hoverfly
  • Introduction
  • Key Concepts
  • Native language bindings
  • Tutorials
  • Basic tutorials
  • Creating and exporting a simulation
  • Importing and using a simulation
  • Adding delays to a simulation
  • Loose request matching using a Request Matcher
  • Using middleware to simulate network latency
  • Simulating HTTPS APIs
  • Running Hoverfly as a webserver
  • Enable CORS support on Hoverfly

This view

  • Original page
  • New address

GeezerVison is showing docs.hoverfly.io — Simulating HTTPS APIs — Hoverfly v1.12.17 documentation

Simulating HTTPS APIs¶

To capture HTTPS traffic, you need to use Hoverfly’s SSL certificate.

First, download the certificate:

wget https://raw.githubusercontent.com/SpectoLabs/hoverfly/master/core/cert.pem

We can now run Hoverfly with the standard capture then simulate workflow.

hoverctl start
hoverctl mode capture
curl --proxy localhost:8500 https://example.com --cacert cert.pem
hoverctl mode simulate
curl --proxy localhost:8500 https://example.com --cacert cert.pem
hoverctl stop

Curl makes the HTTPS request by first establishing a TLS tunnel to the destination with Hoverfly using the HTTP CONNECT method. As curl has supplied Hoverfly’s SSL certificate, Hoverfly is then able to intercept and capture the traffic. Effectively SSL-encrypted communication (HTTPS) is established through an unencrypted HTTP proxy.

Note

This example uses cURL. If you are using Hoverfly in another environment, you will need to add the certificate to your trust store. This is done automatically by the Hoverfly Java library (see Hoverfly Java).

See also

This example uses Hoverfly’s default SSL certificate. Alternatively, you can use Hoverfly to generate a new certificate. For more information, see Configuring SSL in Hoverfly.

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.