change status based on http response header

david.birdsong · 2014-11-18T05:27:16+00:00

Hello! On Mon, Nov 17, 2014 at 12:50 PM, Gaurav Kumar wrote: > Nevermind, I think I answered my own questions. Since Cocockets are not > available, l...

change status based on http response header

david.birdsong

I'm trying to figure out how to change a backend response from an HTTP 200 to an HTTP 404 based on the content_type header.

If I set ngx.status but can't call ngx.exit(ngx.HTTP_OK), will the status code be changed or not?

agentzh

Hello!

On Mon, Nov 17, 2014 at 1:26 PM, David Birdsong wrote:
> I'm trying to figure out how to change a backend response from an HTTP 200
> to an HTTP 404 based on the content_type header.
>
> If I set ngx.status but can't call ngx.exit(ngx.HTTP_OK), will the status
> code be changed or not?
>

Why not just test it out yourself? It should be much simpler than asking here :)

If the behavior does not match the official documentation, please
provide a minimal example that can reproduce the problem. Thank you :)

Regards,
-agentzh

david.birdsong

On Mon, Nov 17, 2014 at 1:57 PM, Yichun Zhang (agentzh) <age...@gmail.com> wrote:

Hello!

On Mon, Nov 17, 2014 at 1:26 PM, David Birdsong wrote:
> I'm trying to figure out how to change a backend response from an HTTP 200
> to an HTTP 404 based on the content_type header.
>
> If I set ngx.status but can't call ngx.exit(ngx.HTTP_OK), will the status
> code be changed or not?
>

Why not just test it out yourself? It should be much simpler than asking here :)

Fair point.

Testing shows that I can change it, but I haven't been able to affect the body size. In my case, this is fine since I'm trying to intercept 0-length 200's from S3 with content-type of 'inode/x-empty'. We suspect their meta data layer is out of sync with their data layer and we're deciding this should be a 404.

If the behavior does not match the official documentation, please
provide a minimal example that can reproduce the problem. Thank you :)

Regards,
-agentzh
.

agentzh

Hello!

On Mon, Nov 17, 2014 at 2:06 PM, David Birdsong wrote:
> Testing shows that I can change it, but I haven't been able to affect the
> body size.

No, assigning to ngx.status will not trigger nginx's special error
page to send. Only ngx.exit() can trigger it (and also only when you
haven't sent any response header yet).

Regards,
-agentzh

david.birdsong

On Mon, Nov 17, 2014 at 2:23 PM, Yichun Zhang (agentzh) <age...@gmail.com> wrote:

Hello!

On Mon, Nov 17, 2014 at 2:06 PM, David Birdsong wrote:
> Testing shows that I can change it, but I haven't been able to affect the
> body size.

No, assigning to ngx.status will not trigger nginx's special error
page to send. Only ngx.exit() can trigger it (and also only when you
haven't sent any response header yet).

Right, this is more in regards to a backend's response body on, what was prior to my change, a 200 response.

Still, simply converting the response code is sufficient for my use case.

Regards,
-agentzh.