Repository navigation
Improvements
HTTP/2
- HTTP/2 server and client follow RFC 9113 more closely, verified with h2spec #3644 #3664 #3665 #3667 #3668 #3669 #3670 #3680
HTTP Transport and Runtime
- Pooled connections and
CONNECTtunnels to HTTP proxies are reused instead of opened anew for every request #3640
Plugins
groovyandjavascript: a failing script sets theabortionReasonproperty, whichabortflows can read. See the tutorialscripting/95-Groovy-Abortion-Reason.yaml#3645
Fixes
OpenAPI
-
multipart/form-dataand form validation:$refrequest body schemas are resolved, also with OpenAPI 3.1 constraints next to the$ref- A missing component is reported as an
openapi-parsingerror - Inline
additionalPropertiesis applied
-
minimum,maximum,exclusiveMinimum/exclusiveMaximumandmultipleOf:- They are checked with exact precision, also for path parameters, form fields, multipart parts and XML values
- They apply only to numbers, as in JSON Schema. Declare
type: integerortype: numberfor untyped parameters
-
An invalid
patternPropertiesregex is reported as anopenapi-parsingerror (500) instead of a400#3663
Plugins
-
groovyandjavascriptin anabortblock now run when there is no response yet #3637 -
javascript#3631:- GraalVM handles script results like Rhino: a result with no value, a string or a number
- Rhino:
console.log()prints all its arguments and prints objects as JSON - Rhino: variables that are declared but not assigned are
undefined
-
prometheus: theversionlabel ofmembrane_infois reported as it is, e.g.7.8.1, so adapt queries that filter on it. Label values are escaped as the text format requires #3686 #3694 -
soapBody, andtemplateloaded from a.json/.xmlfile:pretty: trueformats the output according to its content type #3682 -
sqlInjectionProtection: an unreadable request body gives400and an unreadable response body gives500, both logged atinfo#3711 -
llmGateway: Configured system prompts are added in each provider's own format instead of dropping parts of the client's prompt -
SpEL: built-in functions with numeric parameters accept integer arguments #3678
HTTP Transport and Runtime
- A request body that fails while it is sent to the backend is answered with
400instead of500, and the request is not retried #3710
Configuration and Distribution
- YAML schema:
proxyis allowed at the top level, and list items of abstract types require their element name #3674 #3677
Breaking Changes
JSON and OpenAPI Validation
- JSON bodies with data after the first value, e.g.
{"a":1}{"b":2}or NDJSON, are now rejected byvalidator,openapiandjsonRPCProtection#3663 - JSON Schema
validator:- Bodies are read as UTF-8/16/32 as RFC 8259 requires, and the
charsetparameter is ignored #3663 - Errors no longer contain
node; usepointerinstead. At most 10 errors are reported, plus"errorsTruncated": trueif there are more
- Bodies are read as UTF-8/16/32 as RFC 8259 requires, and the
- OpenAPI
multipart/form-data: a part whose Content-Type is a media range (application/*) is rejected. So is an object or array part with a Content-Type other than JSON or XML, unless itsencodingdeclares that type. A malformed part Content-Type now gives a validation error instead of a500#3663 - OpenAPI XML: with
additionalProperties: false, attributes and child elements that no property maps to are now rejected instead of silently dropped #3663
Plugins
javascript#3631:- GraalVM: each execution runs in its own context. Objects created by the script can't be used after it finishes, so store them with
JSON.stringify(...) - Rhino: whole numbers are passed to Java as floating point (
{"id":7.0}), and a syntax error now stops startup - A script that ends with an array sets the body to that array as JSON
rhino-engine(JSR 223) is no longer bundled. Add it tolibif custom code usesgetEngineByName("rhino")
- GraalVM: each execution runs in its own context. Objects created by the script can't be used after it finishes, so store them with
clusterNotification:/clustermanager/up,/downand/takeoutaccept only POST and answer405otherwise.downandtakeoutanswer404for unknown nodes. See the migration guide #3672cors: settingallowAlltogether withcredentials, or giving an invalid origin, is now a configuration error at startup #3641llmGateway: when policies or a user store are configured, requests the restrictions cannot be applied to are rejected with400. Examples are other endpoints such as/v1/embeddingsor/v1/messages/count_tokens#3675
Dependencies
- OpenTelemetry 1.67.0, Jackson 2.22.4, jose4j 0.9.7, json-smart 2.6.1, Log4j 2.26.1, Spring 7.0.10, Rhino 1.9.2, Groovy 4.0.33 #3704
- commons-codec 1.23.0, commons-io 2.22.0, commons-lang3 3.21.0, Guava 33.8.0-jre, SLF4J 2.0.20, OkHttp 5.5.1, google-api-client 2.9.2, jakarta.activation-api 2.1.4 #3704
- jQuery 3.7.1 in the admin console #3671
Full changelog: 7.8.0...7.8.1