Skip to main content

.NET

.NET is fully supported by Speedscale. Use this page for .NET-specific proxy settings, TLS trust configuration, demo guidance, and the proxymock local workflow.

Kubernetes Sidecar​

When .NET runs with the Speedscale sidecar in forward or dual mode, configure outbound traffic to use the sidecar's forward proxy on 127.0.0.1:4140 unless you changed proxy-out-port.

Typical settings:

export HTTP_PROXY=http://127.0.0.1:4140
export HTTPS_PROXY=http://127.0.0.1:4140

If tls-out is enabled, trust the Speedscale CA separately, commonly with SSL_CERT_FILE on Linux-based .NET containers.

See Proxy Modes and TLS Support for the shared sidecar behavior.

Demo App​

  • Public demo: speedscale/mock-lab (dotnet directory)
  • Stack: .NET minimal API that calls one downstream, the CNCF projects API at https://demo-api.trafficreplay.com
  • Local run: dotnet run
  • Quick validation: ./lab/tests/run_tests.sh --recording

This is the current public .NET demo used for local proxymock examples.

proxymock​

Use this path for the fastest .NET first success on a developer workstation.

  1. 1. Install and initialize proxymock
    brew install speedscale/tap/proxymock
proxymock init

    Use browser sign-in by default. Use `proxymock init --api-key <your key>` only for CI or other headless environments.

  2. 2. Start recording
    git clone https://github.com/speedscale/mock-lab
cd mock-lab/dotnet
proxymock record -- dotnet run

    proxymock records the app while it starts the .NET service as a child process and injects the proxy and TLS settings automatically — HttpClient picks them up with no manual HTTP_PROXY/HTTPS_PROXY exports.

  3. 3. Generate one real workflow
    ./lab/tests/run_tests.sh --recording

    Run the test driver from the repo root. It drives the requests that become the exported production-style trace.

  4. 4. Stop the recording, then run with mocks
    cd mock-lab/dotnet
proxymock mock -- dotnet run

    The mocked run should no longer need live downstream access.

  5. 5. Replay the same traffic against a change
    cd mock-lab/dotnet
proxymock replay --test-against http://localhost:8080

    Use replay as the regression check before shipping .NET changes.

TLS Trust​

On macOS and Linux, modern .NET usually respects SSL_CERT_FILE. See the shared Language Configuration page for the exact command and any platform-specific caveats.