v4.1.1

Fixed

• Multiple HTTP Headers coming from a proxied response are now correctly aggreagated using a , instead of a space. #1489
• Improved the returned path for Problem JSON payloads #1530
• Prism will now consider the first response in the document in case of the absence of a 2XX response, instead of requiring at least a successful response. #1531

Changed

• Prism will now validate that the requested code (either through prefer code header or __code query param) is a number. #1542

v4.1.0

Changed

• When running in proxy mode and an upstream server responds with 501, Prism will now "remock" the request and provide a meaningful response. This is a fancy way to say "if the upstream server has not yet implemented an operation, it will mock" #1426

v4.0.1

Fixed

• Fixed a type issue in the HTTP Client that would let you pass incorrect parameters #1391

v4.0.0

Fixed

• Prism will now refuse to start in case it will detect circular references. #1270

Changed

• Prism is now able to take in consideration all the responses defined for a request (typical in Postman Collection) and respond in a more appropriate way #1310

• BREAKING: The getHttpOperationsFromSpec has been moved from the HTTP Package to the CLI package. If you're using Prism programmatically, this might require some code changes on your side. getHttpOperationsFromResource has been removed. #1009, #1192
• BREAKING: The createClientFromOperations is now exported as export function instead of exporting an object. If you're using Prism programmatically, this might require some code changes on your side #1009
• BREAKING: Prism does NOT support Node 8 and 10 anymore; the miminal runtime is now 12
• A significant number of dependencies has been upgraded

v3.3.7

Fixed

• Prism's Proxy feature will stop proactively requesting Compressed responses, following what is really in the OAS document #1309,#1319

Changed

• Prism is now stop to claim error for paths declared in the document that are not starting with a / #1340

v3.3.6

Fixed

• Prism is not returning an error anymore when trying to construct a schema for HTTP headers and query string with mixed cases property names #1268

v3.3.5

Fixed

• Since the media type parameters are not standardised (apart from the quality one), the negotiator will discard them during the matching process or simply treat them as strings/numbers without trying to guess anything more #1159
• Prism is now handling correctly hypens on both Path parameters and Query Parameters #1189, #1992

v3.3.4

Fixed

• The mock diagram has been updated to include the security validations #1141
• Prism will now correctly refuse invalid requests even when used with the proxy command with the --errors flag #1101
• Autogenerated security validation errors now have the detail field filled with an informative message #1101
• Correctly catch some exceptions and propagate them to the CLI #1107

v3.3.3

Fixed

• All the dependencies used by the various Prism packages have been explicitily declared avoiding some resolutions problems in case you are using Prism programmatically #1072
• Prism's current options aren't overriden internally anymore because of the Prefer header set #1074

v3.3.2

Fixed

• Prism will not correctly consider that HTTP Security Schemes are case insensitive #1044