nginx

Is there an existing issue for this?

• I have searched the existing issues

Kong version ($ kong version)

2.5.1.0

Current Behavior

When calling kong.response.exit(), the function automatically sets the Content-Length header on the response even if the Transfer-Encoding header is present. This is in violation of RFC 7230 3.3.2:

A sender MUST NOT send a Content-

custom errors image needs to be promoted.

Steps:

• Open a PR for https://github.com/kubernetes/k8s.io/blob/main/k8s.gcr.io/images/k8s-staging-ingress-nginx/images.yaml#L129, add a new line below this one with the following:

 "sha256:1d69f28d6412b0f2a6302f9df9a6bc49e83703336a35f95ab109cad10e039120": ["1.0.0"]

• Once this PR gets merged, open a new PR in ingress-nginx repo to updat

Issue description

Now, when configure radixtree_uri_with_parameter in config.yaml, it only work on Route.
If you want use path parameter with control api, you must change source code.
Could you provide an optional way to configure it without change source code just like radixtree_uri_with_parameter.lua

Environment

• all version

I use naxsi with nginx. I want to add request id which is used by nginx to nginx error logs when blocked by naxsi. Is it possible ? Thanks for help.

Describe the bug

There is a bug in podinfo chart which will not deploy service if you enabled canary, even though you enabled service via helm values.

https://github.com/fluxcd/flagger/blob/main/charts/podinfo/templates/service.yaml#L1

To Reproduce

If you set values like this, it will not deploy service.

service:
  enabled: true # service will not be deployed if ca