Populært: Data oppdatert 16. november 2026

Kategorier

Internett1 415
Kommunikasjon328
Lyd og video937
Grafikk og design561
Kontor og produktivitet1 177
Utviklerverktøy3 280
KI-verktøy605
Sikkerhet og personvern407
Systemverktøy3 183
Spill544
Utdanning og vitenskap241
Nettverk og IT292

Last ned Mockzilla 2.8.1

OpenAPI mock server with realistic responses, request validation, latency and error simulation, and upstream proxy fallback

Dette er en eldre versjon. Nyeste versjon er 2.11.2. Mockzilla 2.11.2 · Utgitt:

Installasjonsfiler 2.8.1

ArkitekturTypeOmfangFilstørrelseNedlastingSHA256
64-bit Portabel — — github.com VirusTotal
ARM64 Portabel — — github.com VirusTotal

Lenken og SHA256-summen kommer fra fellesskapsmanifestet til Windows Package Manager. Sammenlign sjekksummen for den nedlastede filen før du kjører den.

Endringslogg

What's Changed
Take response values from the incoming request by @jbn2336mz in #56
Context values can be pulled out of the request being answered, using a dotted path into its payload:
charge:
currency: "request:order.payment.amount.currency"
amount: "request:order.payment.amount.value"
Post an order with EUR and 10.5 and the mock answers with EUR and 10.5 instead of random data. Array elements are addressed by index: request:order.amounts[0].currency.
- Works wherever contexts work: service context.yml, the X-Mockzilla-Context header, the UI context editor, and inside area blocks such as in-response.
- JSON and form-encoded requests are both read; the Content-Type header decides. Form bodies keep their nesting, so order[payment][currency]=EUR is reached with request:order.payment.currency.
- A path that matches nothing falls back to generated data, and the value has to fit the schema of the field it fills.
Fix response header generation by @jbn2336mz in #57
An in-response-header block used to be ignored, so headers meant to carry a fixed request id or trace id came back as random words. Those blocks now take effect, and in-response applies to response headers too.
Headers declared readOnly in the spec were dropped and sent as the literal text <nil>; they now appear with their value. Headers declared writeOnly were sent as <nil> as well; they are now omitted.
The documented area priority never matched the actual behavior, for requests as well as responses. The real chain is:
in-request-header > in-request > in-header > root
in-response-header > in-response > in-header > root
A header falls back to its direction (in-request / in-response) before the direction-agnostic in-header.
Full Changelog: v2.8.0...v2.8.1

https://github.com/mockzilla/mockzilla/releases/tag/v2.8.1

Mest populær i Programmeringsspråk og SDK-er

Se alle
  1. Go Programming LanguageProgrammeringsspråk og SDK-er
  2. LLVMProgrammeringsspråk og SDK-er · LLVM
  3. DenoProgrammeringsspråk og SDK-er · Deno Land Inc.
  4. CMakeProgrammeringsspråk og SDK-er · Kitware
  5. YarnProgrammeringsspråk og SDK-er · Yarn Contributors
  6. pnpmProgrammeringsspråk og SDK-er · pnpm
  7. CcacheProgrammeringsspråk og SDK-er · Joel Rosdahl
  8. sbtProgrammeringsspråk og SDK-er · Lightbend, Inc.
  9. BOINCProgrammeringsspråk og SDK-er · Space Sciences Laboratory, U.C. Berkeley
  10. Dart SDKProgrammeringsspråk og SDK-er · Google

Stikkord

Del