Previously, Peaky tests assigned their URIs using the URI scheme of the incoming requests, so that the same configuration would be valid whether the hosting service was exposed via HTTP or HTTPS. This doesn't work for reverse proxies since the outward-facing URI could be HTTPS but the hosted service receives a proxied HTTP request.
The current change allows for tests defined with https:// URIs to be advertised with https:// URIs even when the service sees incoming http:// requests.
Previously, Peaky tests assigned their URIs using the URI scheme of the incoming requests, so that the same configuration would be valid whether the hosting service was exposed via HTTP or HTTPS. This doesn't work for reverse proxies since the outward-facing URI could be HTTPS but the hosted service receives a proxied HTTP request.
The current change allows for tests defined with
https://URIs to be advertised withhttps://URIs even when the service sees incominghttp://requests.