Skip to content

v7.8.1

Latest

Choose a tag to compare

@github-actions github-actions released this 05 Nov 10:38
· 1 commit to 8e7db5b2e618f20d6c35f55335583e6b2c012ffb since this release

Improvements

HTTP/2

HTTP Transport and Runtime

  • Pooled connections and CONNECT tunnels to HTTP proxies are reused instead of opened anew for every request #3640

Plugins

  • groovy and javascript: a failing script sets the abortionReason property, which abort flows can read. See the tutorial scripting/95-Groovy-Abortion-Reason.yaml #3645

Fixes

OpenAPI

  • multipart/form-data and form validation:

    • $ref request body schemas are resolved, also with OpenAPI 3.1 constraints next to the $ref
    • A missing component is reported as an openapi-parsing error
    • Inline additionalProperties is applied

    #3663

  • minimum, maximum, exclusiveMinimum/exclusiveMaximum and multipleOf:

    • 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: integer or type: number for untyped parameters

    #3663

  • An invalid patternProperties regex is reported as an openapi-parsing error (500) instead of a 400 #3663

Plugins

  • groovy and javascript in an abort block 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: the version label of membrane_info is 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, and template loaded from a .json/.xml file: pretty: true formats the output according to its content type #3682

  • sqlInjectionProtection: an unreadable request body gives 400 and an unreadable response body gives 500, both logged at info #3711

  • llmGateway: Configured system prompts are added in each provider's own format instead of dropping parts of the client's prompt

    #3675 #3698

  • 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 400 instead of 500, and the request is not retried #3710

Configuration and Distribution

  • YAML schema: proxy is 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 by validator, openapi and jsonRPCProtection #3663
  • JSON Schema validator:
    • Bodies are read as UTF-8/16/32 as RFC 8259 requires, and the charset parameter is ignored #3663
    • Errors no longer contain node; use pointer instead. At most 10 errors are reported, plus "errorsTruncated": true if there are more
  • 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 its encoding declares that type. A malformed part Content-Type now gives a validation error instead of a 500 #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 to lib if custom code uses getEngineByName("rhino")
  • clusterNotification: /clustermanager/up, /down and /takeout accept only POST and answer 405 otherwise. down and takeout answer 404 for unknown nodes. See the migration guide #3672
  • cors: setting allowAll together with credentials, or giving an invalid origin, is now a configuration error at startup #3641
  • llmGateway: when policies or a user store are configured, requests the restrictions cannot be applied to are rejected with 400. Examples are other endpoints such as /v1/embeddings or /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