symplyf opened a new issue, #560:
URL: https://github.com/apache/apisix-helm-chart/issues/560
Hi,
I started using `APISIX`, and everything works fairly smooth out of the box.
I managed to get `cert-manager` to work as well.
However, after enabling `gateway.ingress` I started running into `400 Bad
Request - Request Header Or Cookie Too Large` errors.
`values.yaml`:
`
gateway:
ingress:
enabled: true
className: "apisix"
annotations: {
cert-manager.io/cluster-issuer: letsencrypt
}
hosts:
- host: api.domain.ltd
paths: [/*]
tls:
- secretName: api-domain-ltd-tls
hosts:
- api.domain.ltd
`
After some debugging I realize that what's going on is that the `upstream`
of the `/*` route created by `apisix-ingress-controller` is using `pass_host:
pass` which results in a loop, and the `400 Bad Request` occurs after `n` tries.
At least, that's the theory, since changing it to `pass_host: node` solves
the problem, and this is replicable through the `apisix pod`. Solving the
problem in the sense that it will return `{"error_msg":"404 Route Not Found"}`.
Anyway, what is the recommended way to deal with this situation? Am I
supposed to use a different `path`, patch the `upstream`, or am I missing
something entirely?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
