このページは、まだ日本語ではご利用いただけません。翻訳中です。
古いプラグインバージョンのドキュメントを閲覧しています。
Changelog
Kong Gateway 3.8.x
- Fixed an issue where the plugin couldn’t obtain the value when the path parameter name contained hyphen characters.
- Fixed an issue where parameter serialization didn’t behave the same as in the OpenAPI specification.
- Fixed an issue where the non-string primitive types passed via URL query were unexpectedly cast to string when the OpenAPI spec version was v3.1.0.
Kong Gateway 3.7.x
- Added the new field
api_spec_encoded
to indicate whether theapi_spec
is URI-Encoded. - Add the
custom_base_path
field to specify a custom base path. Use it with thedeck file namespace
command. - The plugin now supports OpenAPI Specification v3.1.0. The plugin now switches to a new JSON Schema validator when the specification version is v3.1.0.
Kong Gateway 3.6.x
- The plugin now bypasses schema validation when the content type is not
application/json
. - Fixed a bug where the plugin throws a runtime error caused by the ref parameter schema not being dereferenced.
- Exposed metrics for serviceless routes.
- Fixed an issue where the plugin threw a runtime error while validating parameters with the AnyType schema and style keyword defined.
- Fixed an issue where the cookie parameters weren’t being validated.
- Fixed an issue where the
nullable
keyword didn’t take effect. - Fixed an issue where the request path couldn’t matched when containing regex escape characters. The URI component escaped characters were incorrectly unescaped.
Kong Gateway 3.5.x
- Added a new property
include_base_path
for path match evaluation. Path parameters can now correctly match non-ASCII characters. - Fixed an issue where non
application/json
content-types were being rejected, even when the request body was not required. - Fixed an issue where a null pointer exception could occur in certain scenarios
when
notify_only_request_validation_failure
was set to true. - Fixed an issue where valid recursive schemas were always rejected.
Kong Gateway 3.4.x
- Fixed an issue where the plugin was unable to pass the validation even if path parameter was valid.
- Fixed an issue where the plugin always validated the request body even
if the method spec had no
requestBody
defined. - Fixed an issue where the comparison between large absolute value numbers could be incorrect due to the number being converted to exponential notation.