incorrect response status?

pongongxlua · 2014-03-12T23:16:28+00:00

Hello! On Mon, Mar 10, 2014 at 11:33 PM, Mathew Heard wrote: > How is the lua modules position in the body filter chain determined? > Just as any oth...

incorrect response status?

pongongxlua

Hi,

I am trying to read the ngx.status in the header_filter_by_lua_file so I can be sure to modify things only when the response is 206. The code is:

if (ngx.status == 206) then

-- changes go here

else

ngx.log(ngx.EMERG, ngx.status);

end

curl sees a 206 response, but i see only a log message of 200. The location contains just a rewrite_by_lua_file and this header_filter_by_lua_file. Am i looking in the wrong place?

thanks

Pongo

agentzh

Hello!

On Wed, Mar 12, 2014 at 8:16 AM, Pongo wrote:
>  I am trying to read the ngx.status in the header_filter_by_lua_file so I
> can be sure to modify things only when the response is 206.
[...]
>   curl sees a 206 response, but i see only a log message of 200. The
> location contains just a rewrite_by_lua_file and this
> header_filter_by_lua_file. Am i looking in the wrong place?
>

Sorry, but I don't quite follow your reasoning here.

Will you provide a minimal but still *complete* example along with the
steps to reproduce what you believe is a bug? Please remove as many
external dependencies as possible so that I can run your test case on
my side.

Thanks!
-agentzh

pongongxlua

Hi agentzh,

Here is the minimal configuration example that should help reproduce the bug, nginx version: nginx/1.4.5 built by gcc 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5.1)

configure arguments: --prefix=../httpd --add-module=/home/pongo/src/ngx_devel_kit-0.2.19 --add-module=/home/pongo/src/lua-nginx-module-0.9.5rc2 --without-http_gzip_module --with-debug

The location in the nginx.conf contains the following line:

header_filter_by_lua_file /path/to/lua/file.lua

and the lua file contains only one line:

ngx.log(ngx.EMERG, "--------<" .. ngx.status .. ">------")

I do a curl like so: curl -D - -H "Range: bytes=10-1000" -O http://hostname:8080/file.m4v

on the client this prints:

TP/1.1 206 Partial Content

Server: nginx/1.4.5

Date: Thu, 13 Mar 2014 11:30:27 GMT

Content-Type: video/x-m4v

Content-Length: 991

Last-Modified: Tue, 11 Mar 2014 14:53:27 GMT

Connection: keep-alive

ETag: "531f2367-14a22b6"

Content-Range: bytes 10-1000/21635766

but in the nginx log, i see:

2014/03/13 12:30:27 [emerg] 22527#0: *6 [lua] out.lua:1: --------<200>------ while sending response to client, client: 192.168.2.100, server: localhost, request: "GET /file.m4v HTTP/1.1", host: "hostname:8080"

I have changed only the hostname and file location in the info above. I expected ngx.status to be 206 instead of 200. Is that a bug?

with best regards

Pongo

On Wed, Mar 12, 2014 at 10:32 PM, Yichun Zhang (agentzh) <age...@gmail.com> wrote:

Hello!

On Wed, Mar 12, 2014 at 8:16 AM, Pongo wrote:
> I am trying to read the ngx.status in the header_filter_by_lua_file so I
> can be sure to modify things only when the response is 206.

[...]

> curl sees a 206 response, but i see only a log message of 200. The
> location contains just a rewrite_by_lua_file and this
> header_filter_by_lua_file. Am i looking in the wrong place?
>

Sorry, but I don't quite follow your reasoning here.

Will you provide a minimal but still *complete* example along with the
steps to reproduce what you believe is a bug? Please remove as many
external dependencies as possible so that I can run your test case on
my side.

Thanks!
-agentzh

.

agentzh

Hello!

On Thu, Mar 13, 2014 at 4:45 AM, Pongo Lua wrote:
> header_filter_by_lua_file /path/to/lua/file.lua
>
> and the lua file contains only one line:
> ngx.log(ngx.EMERG, "--------<" .. ngx.status .. ">------")
>
[...]
> 2014/03/13 12:30:27 [emerg] 22527#0: *6 [lua] out.lua:1: --------<200>------

This is not a bug; it is the expected behavior.

As I've already said in another thread (also initiated by you
yesterday), the 206 status code is set by nginx's standard range
filter module, which always runs after header_filter_by_lua. So what
you see in header_filter_by_lua is the original response status code
(right before it gets changed to 206 by the range filter module).

Regards,
-agentzh

pongongxlua

I understand now! Thank you. I did not make the connection earlier between the 206 and the range_filter module rewriting the 200 to 206.

regards

Pongo

On Thu, Mar 13, 2014 at 5:16 PM, Yichun Zhang (agentzh) <age...@gmail.com> wrote:

Hello!

On Thu, Mar 13, 2014 at 4:45 AM, Pongo Lua wrote:
> header_filter_by_lua_file /path/to/lua/file.lua
>
> and the lua file contains only one line:
> ngx.log(ngx.EMERG, "--------<" .. ngx.status .. ">------")
>

[...]

> 2014/03/13 12:30:27 [emerg] 22527#0: *6 [lua] out.lua:1: --------<200>------

This is not a bug; it is the expected behavior.

As I've already said in another thread (also initiated by you
yesterday), the 206 status code is set by nginx's standard range
filter module, which always runs after header_filter_by_lua. So what
you see in header_filter_by_lua is the original response status code
(right before it gets changed to 206 by the range filter module).

Regards,

-agentzh.