Connections
Each of these has a page of its own in Settings. Open Settings with Reqly › Settings… (⌘,) on the Mac, or with the gear button at the right end of the title bar (Ctrl+,) on Windows.
Upstream proxy
Section titled “Upstream proxy”For networks that reach the internet only through another proxy, as many offices do.
- In Settings, choose Upstream Proxy, and turn on Use an upstream proxy.
- Enter its Server and Port, and a User name and Password if it asks for them.
- Under Reach Directly, list the hosts that shouldn’t go through it, separated by commas, spaces or new lines. Patterns such as
*.corp.example.comwork. Addresses on the local network are reached directly too, unless you turn that off. Your Mac itself always is. - Click Apply.
- In Settings, choose Upstream proxy, and turn on Use an upstream proxy.
- Enter its Server and Port, and a User name and Password if it asks for them.
- Under Reach directly, list the hosts that shouldn’t go through it, separated by commas, spaces or new lines. Patterns such as
*.corp.example.comwork. Addresses on the local network are reached directly too, unless you turn that off. Your PC itself always is. - Click Apply.
Reqly works with HTTP proxies, with or without a user name and password. It keeps the password in your keychain on the Mac, and encrypted for your Windows account on Windows. While Reqly captures, the status bar shows Via and the proxy’s address. A request’s Overview shows the upstream proxy it went through.
Reverse proxies
Section titled “Reverse proxies”For apps that can’t use a proxy. You point the app at a local address, such as http://localhost:8080, and Reqly sends every request it gets there on to one server, and records it.
- In Settings, choose Reverse Proxy, and click +.
- Enter a Local port, and the Server the requests go to, such as
https://api.example.com. - Click Add.
- Point the app at
http://localhostand the port you chose.
- In Settings, choose Reverse proxy, and click Add reverse proxy.
- Enter a Local port, and the Server the requests go to, such as
https://api.example.com. - Click Add.
- Point the app at
http://localhostand the port you chose.
Reverse proxies listen only while Reqly captures, and only your computer can reach them. When the server’s address starts with https://, Reqly connects to it over HTTPS. Keep redirects on this address, which is on to begin with, points the server’s redirects back at the local address, so the app keeps going through Reqly.
Client certificates
Section titled “Client certificates”For servers that ask apps to identify themselves with a certificate.
- In Settings, choose Client Certificates, and click +.
- Enter the Hosts to present it to, such as
api.example.com.*.example.comcovers the subdomains of example.com, but not example.com itself. - Click Choose…, and pick the certificate: a
.p12or.pfxfile, as Keychain Access exports, or PEM files with the certificate and its private key. If the file is locked, enter its Password. - Click Add.
- In Settings, choose Client certificates, and click Add client certificate.
- Enter the Hosts to present it to, such as
api.example.com.*.example.comcovers the subdomains of example.com, but not example.com itself. - Click Choose…, and pick the certificate: a
.p12or.pfxfile, or PEM files with the certificate and its private key. If the file is locked, enter its Password. - Click Add.
Reqly keeps certificates and their private keys in your keychain on the Mac, and encrypted for your Windows account on Windows. It doesn’t keep the file’s password.
Reqly presents a certificate where it makes the secure connection itself: for hosts it decrypts, for reverse proxies to https:// servers, and for requests you send from Reqly. If a server asks for a certificate that Reqly doesn’t have, the request says so.