nginx

expected result:
example.com?param=abc -> will become example.com
example.com/?param=abc -> will stay example.com/

actual result:
example.com?param=abc -> become example.com
example.com/?param=abc -> stays example.com/?param=abc

Some e2e check that no error occurs, but don't check if the message equals an expected value. We could improve that

Affected files is https://github.com/kubernetes/ingress-nginx/blob/main/test/e2e/admission/admission.go

/triage accepted
/priority backlog
/good-first-issue

Percona is quite strict on having primary keys on all tables (and rightly so).
Please add primary keys to all tables, even if it's just an auto-increment.

It's mostly just the following tables:
authentication_logs (could just get a auto-increment primary key added)
identity_verification_tokens (could just set the token as primary key)

Improved or typo fixed.

Not yet. Added to the documentation, such as chapters on multi-language and WASM.

Solution

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