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-

For a better overview and transparency we should add column to the supported versions overview table that contains the helm version. That way it is easy to see which helm version includes which nginx ingress version.

/kind documentation

Improved or typo fixed.

Currently, the README claims that the WASM extension is the modern way. However, it is an experimental feature.

Solution

Need to fix it with:

diff --git README.md README.md
index d14aae9c..8e11456c 100644
--- README.md
+++ README.md
@@ -146,10 +146,10 @@ A/B testing, canary release, blue-green deployment, limit rate, defense against
   - Custom routing

Under edit Proxy Host, it states to use 1.1.1.1/path for sub folder forwarding

1.1.1.1 should not be used like this, as its a valid external address and website

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