---
title: "ngx_mruby v2.7.10"
language: "en"
documentation_version: "2.x"
channel: "maintenance"
release_context: {"latest_release_tag":"v2.7.12","unreleased_versions":[],"latest_release_revision":"49d26b879df732f8260f8454b90b0774789ef818"}
source_revision: "49d26b879df732f8260f8454b90b0774789ef818"
working_tree_clean: true
source_path: "docs/releases/v2.7.10.md"
source_sha256: "c2f0ccd2a43bf3ee994f104be03c38cadcc4f683a7ebdf78620d1fdee07025f6"
source_at_revision: true
source_url: "https://github.com/matsumotory/ngx_mruby/blob/49d26b879df732f8260f8454b90b0774789ef818/docs/releases/v2.7.10.md"
html_url: "https://ngx.mruby.org/v2/releases/v2.7.10/"
markdown_url: "https://ngx.mruby.org/v2/markdown/releases/v2.7.10.md"
last_updated: "2026-11-16"
---

# ngx_mruby v2.7.10

## Behavior changes: read before upgrading

None.

## New features

None.

## Fixes

- An SSI page that includes, after another include, a location with an mruby body filter whose body was written with `Nginx.rputs` or `Nginx.echo` (by its content handler, or by a rewrite handler before the request went on to the content) gets its whole response. Before, the client got at most the part of the page before that include, and nginx closed the connection after `send_timeout`. nginx keeps the output of such an include until the includes before it are sent, and then calls its filters again with no new data to send it; the body filter took these calls for the start of a new body and held them back (#827)
- A location with `mruby_add_handler on` and `mruby_cache on` terminated the worker on a request to a script file under it. `mruby_add_handler` builds a fresh mruby code from the request path on every request, so it has to be compiled on every request; the cached run skipped the compile and the code reached the handler with no compiled proc. The content handler now runs a `mruby_add_handler` code as not cached, so the script runs (#829)
- A file-based mruby handler shared across locations with different `mruby_cache` settings — a server-level handler with no cache keyword, inherited by a location with `mruby_cache on` and one without — now keeps its recompiled proc valid for the location that caches it. Before, the location without `mruby_cache on` recompiled the shared handler, and the caching location could reuse a proc that was no longer valid ([GHSA-2hc3-r8g9-9f9x](https://github.com/matsumotory/ngx_mruby/security/advisories/GHSA-2hc3-r8g9-9f9x))

## Build and test changes

- `test/t/cases/ssi_body_filter.rb` requests three more SSI pages of `test/conf/conf.d/91-ssi-body-filter.conf` (port 18146), each of which includes a static file and then a location whose body comes from `Nginx.rputs` and goes through a body filter: a content handler, the same with a header filter, and a static file after a rewrite handler that writes with `Nginx.rputs` and declines (#827)
- `test/t/cases/add_handler_cache.rb` (with `test/conf/conf.d/98-add-handler-cache.conf`, port 18120, and `test/html/add_handler_cache.rb`) requests a script under a location with `mruby_add_handler on` and `mruby_cache on` (#829)
- `test/t/cases/shared_handler_cache.rb` (with `test/conf/conf.d/99-shared-handler-cache.conf`, port 18121, and `test/html/shared_handler_cache.rb`) alternates requests to two locations that share a server-level file content handler and differ in `mruby_cache` ([GHSA-2hc3-r8g9-9f9x](https://github.com/matsumotory/ngx_mruby/security/advisories/GHSA-2hc3-r8g9-9f9x))

## Upgrading

- No directive was added, renamed or removed. Rebuild the module with this
  release the way you built 2.7.9, and replace the binary or the dynamic
  module as usual. `Nginx.module_version` returns `2.7.10`.

Nothing else needs to be checked before upgrading: this release has no
behavior change.
