From a378f6aa3136ed7ef172b71add31ee62e560df00 Mon Sep 17 00:00:00 2001 From: Zhidao HONG Date: Thu, 25 May 2023 00:27:55 +0800 Subject: HTTP: fixed variable caching. When a variable is accessed in the Unit configuration, the value is cached. This was useful prior to the URI rewrite feature, but now that the URI (more precisely, the request target) can be rewritten, the contents of the variable $uri (which contains the path part of the request target, and is decoded) should not be cached anymore, or at least the cached value should be invalidated after a URI rewrite. Example: { "rewrite": "/prefix$uri", "share": "$uri" } For a request line like GET /foo?bar=baz HTTP/1.1\r\n, the expected file served in the response would be /prefix/foo, but due to the caching issue, Unit currently serves /foo. --- docs/changes.xml | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'docs/changes.xml') diff --git a/docs/changes.xml b/docs/changes.xml index 14e65672..29c5c995 100644 --- a/docs/changes.xml +++ b/docs/changes.xml @@ -32,6 +32,12 @@ NGINX Unit updated to 1.31.0. date="" time="" packager="Nginx Packaging <nginx-packaging@f5.com>"> + + +ensure that $uri variable is not cached. + + + deprecated options were unavailable. -- cgit