You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the desired outcome from the user's perspective
When the browser interacts with an HTTP endpoint it sends a lot fo header information causing a 400 error code. This can be alleviated with the run param -Pzilla.binding.kafka.client.produce.record.framing.size=1024.
Acceptance criteria
Update the default value to be more resilient
Publish an event with the failure reason of "Header size too large"
Here is the /var/run/zilla dir from reproducing this issue with the same request. The first request went directly to zilla and the second went through the ingress-nginx controller and caused the 400 error. zilla-7954b94d6d-h2sbx.tar.gz
The text was updated successfully, but these errors were encountered:
Describe the desired outcome from the user's perspective
When the browser interacts with an HTTP endpoint it sends a lot fo header information causing a
400
error code. This can be alleviated with the run param-Pzilla.binding.kafka.client.produce.record.framing.size=1024
.Acceptance criteria
Here is the
/var/run/zilla
dir from reproducing this issue with the same request. The first request went directly to zilla and the second went through the ingress-nginx controller and caused the 400 error.zilla-7954b94d6d-h2sbx.tar.gz
The text was updated successfully, but these errors were encountered: