Deleting Set-Cookie response header

ok, first - don't try to find a sense in this code - but it does not behave as it is expected:

i have a php-script which is used via fastcgi in nginx and will only execute this:

<?php
setcookie("TestCookie1", "foo");
setcookie("TestCookie2", "bar");

phpinfo();
?>

When using rewrite_by_lua_file with this code something unexpected happens:

if ngx.is_subrequest == false then

        ngx.header["Set-Cookie"] = {}
        res = ngx.location.capture(ngx.var.uri)

        for i,j in pairs(res.header) do ngx.header[i] = j end

        ngx.send_headers()
        ngx.print(res.body)

end

Normally i thought that the "for .. pairs"-part will write all response-headers from the subrequest into the ngx.header-table again. but in the Set-Cookie header only "TestCookie2" is received by the client which starts the request...

[agentzh]

I'll look into this shortly :) Thanks a lot for the report!

[agentzh]

it seems that the offending line is

ngx.header["Set-Cookie"] = {}

By commenting out this line, your example works as expected. It seems that ngx.header.foo = {} has some bugs. I'll investigate it today ;)

Thanks!

Hi,
that was my point - think my discription was a bit inaccurate.

When deleting a response-header-table like ngx.header["Set-Cookie"] = {} it works fine if it is the last action you perform on this header.
If other actions are performed like setting the header again with the information from the subrequest (which is a php-application that sets multiple cookies) some parts are gone missing :)

... looking in the module-source by myself, too :-)

Btw. eventually it should be mentioned in the readme, that ngx.header[] = ... won't have any effect, if ngx.print (or something similar) was performend once before (this behaviour is normal i guess, but it did cost me some minutes to find out why something was not working :) ) / Sorry, if it's already in the readme - i looked and at least it's not in the ngx.header-part

[agentzh]

On Thu, May 19, 2011 at 5:02 PM, moodydeath
reply@reply.github.com
wrote:

Hi,
that was my point - think my discription was a bit inaccurate.

When deleting a response-header-table like ngx.header["Set-Cookie"] = {} it works fine if it is the last action you perform on this header.
If other actions are performed like setting the header again with the information from the subrequest (which is a php-application that sets multiple cookies) some parts are gone missing :)

... looking in the module-source by myself, too :-)

Just fixed it in master. Please check it out ;)

Will also port this fix back to ngx_headers_more. It also has this issue ;)

Thanks a lot!
-agentzh