Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"status 000" sometimes occurs when using eval with proxy_pass #15

Open
pmarks-net opened this issue Nov 11, 2019 · 0 comments
Open

"status 000" sometimes occurs when using eval with proxy_pass #15

pmarks-net opened this issue Nov 11, 2019 · 0 comments

Comments

@pmarks-net
Copy link

We were using nginx-eval-module with NGINX 1.16.0 and a configuration of this form:

location / {
  proxy_pass https://some_upstream_server/;

  eval_override_content_type application/octet-stream;
  eval $foo {
    proxy_pass http://foo;
    proxy_pass_request_headers off;
  }
  proxy_set_header Authorization $foo;
}

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant