You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clients send us POST requests, the eval module fetches a value, and we attach a header before forwarding the request.
Some fraction of the time, for some fraction of client implementations, NGINX would simply close the incoming TCP connection, while logging these values:
$status "000"
$upstream_status "-"
Lines like this also appeared in the --debug log:
*517 http client request body rest 217
*517 http client request body recv -2
I'm not trying to debug this anymore, because "This module is experimental and production use is discouraged", and the problem went away when I replaced eval with rewrite_by_lua_block + ngx.location.capture().
I'm just posting this in case someone encounters similar errors in the future.
The text was updated successfully, but these errors were encountered:
We were using nginx-eval-module with NGINX 1.16.0 and a configuration of this form:
Clients send us POST requests, the eval module fetches a value, and we attach a header before forwarding the request.
Some fraction of the time, for some fraction of client implementations, NGINX would simply close the incoming TCP connection, while logging these values:
Lines like this also appeared in the --debug log:
I'm not trying to debug this anymore, because "This module is experimental and production use is discouraged", and the problem went away when I replaced
eval
withrewrite_by_lua_block
+ngx.location.capture()
.I'm just posting this in case someone encounters similar errors in the future.
The text was updated successfully, but these errors were encountered: