Kong plugin file-log always logs response connection header as close about kong

[ms2008]

This is a known issue, but it's actually a Nginx defect that has existed for almost 10 years.

Ref: https://trac.nginx.org/nginx/ticket/1850

[StarlightIbuki]

The file-log does not customize the behavior of header fetching, and it's calling the original vanilla API ngx.req.get_header.
You could debug this issue with tapping tools to confirm the actual received request.

[mohittevatia]

Okay thanks for your reply, let me revert with more details

[StarlightIbuki]

@mohittevatia Thanks for spending time on this. We will investigate it.
This seems unlogical and probably is a bug.

[mohittevatia]

Great thanks a lot. Let me know if there is anything needed.

I had used the Admin port, should have used 8000 (public) one. But it was same behaviour on that too.

[mohittevatia]

Oh i see, thank you linking this issue. Would you recommend any other workaround or fix to exports the logs of kong? Recommend plugin for the time being?

[ms2008]

I'm afraid there isn't any workaround for this yet unless you patch Nginx, but that's risky.

[StarlightIbuki]

Closing as this cannot be fixed from Kong's side.