- Support mutating stubs without restarting the imposter. See the API overview page for details on the new API calls.
- Support using injection to generate predicates during proxying.
- Support adding a passphrase when proxying to HTTPS servers.
passphrasefield in the updated contract
- Support selecting the TLS protocol to use for legacy integrations when proxying to HTTPS servers.
secureProtocolfield in the updated contract
- Inner quotes were not correctly escaped on
shellTransformbehaviors. Passing the request and response JSON on the command line proved to be difficult in a cross-platform way. The interface now passes environment variables instead. The old interface is maintained for backwards compatibility, but only the environment variables guarantee correct quoting. See the updated docs.
- Fix improper mangling on binary HTTP request bodies.
- No longer rewrites empty query params without a value during proxying (previously, https://server.example.com/service?WSDL was rewritten to https://server.example.com/service?WSDL=)
- Removed a dependency with a restrictive EUPL license (changed mailparser to mailparser2 for a more permissive license)
- Fix parsing application/x-www-form-urlencoded request body when its content-type header name is in lowercase
- Preventing "except" parameter from modifying "matches" predicate pattern
Many thanks to the following kind folks for help with this release, either through bug reports, suggestions, or direct code contributions:
- Connor Worley
- Pavel Yaschenko
- Colin Schoen
- Authapon Kongkaew
- Colin Newell
- Scott Bloch-Wehba-Seaward
npm install -g firstname.lastname@example.org
|Option||node.js required?||sudo required?||links||Description|
|Self-contained archives||No||No||Simply unpack and run
|source tarball||Yes||No||source tarball if you roll that way.|
Windows path limitations
*mountebank wishes very much for your Windows experience to be hassle-free, but he is simply not qualified to address a particular constraint of Windows Explorer. For legacy reasons, some Windows applications, including most notably Windows Explorer, have a maximum number of characters allowed in a path of 260 characters. As mountebank writes these words, the longest path he includes in the zip files is around 175 characters. The zip file name, which is likely to represent itself as two nested directories if you use the defaults to unzip it, will be around 25 characters. That gives you very little wiggle room. If you unzip the file in your users directory, you may very likely get an error because of this constraint.
The following solutions will all work:
- Unzip to the root of your C: drive (or a similar small path)
- Use 7zip to unzip the file instead of Windows Explorer
npmto install mountebank instead of the zip file