mcupei opened a new issue, #13673:
URL: https://github.com/apache/apisix/issues/13673

   ### Current Behavior
   
   ## Summary
   
   Chunked-Transfer-Encoding POST requests are rejected with **`413 Request 
Entity Too Large`**
   by `apache/apisix:3.17.0-redhat`, while the identical request against
   `apache/apisix:3.16.0-redhat` succeeds. Requests using a `Content-Length` 
header (no
   chunked encoding) work correctly on **both** versions.
   
   ### Expected Behavior
   
   Chunked-Transfer-Encoding POST requests are working like before.
   
   ### Error Logs
   
   _No response_
   
   ### Steps to Reproduce
   
   This was reproduced in a k3d
   (Kubernetes) cluster with both images running side-by-side with 
byte-for-byte identical
   APISIX route configuration — the only variable was the container image tag.
   
   ### Environment
   
   - k3d v5.9.0 cluster (`apisix-test`), local registry at 
`apisix-registry:5000`
   - APISIX deployed in **standalone mode** (`config_provider: yaml`, no etcd) 
so both
     versions run from an identical `apisix.yaml` / `config.yaml`
   - Upstream: `mendhak/http-https-echo:31`, echoes back method/headers/body as 
JSON
   - Route: `uri: /*` → `echo-upstream.apisix-test.svc.cluster.local:80`
   - Manifests: `k8s/namespace.yaml`, `k8s/apisix-configmap.yaml`, 
`k8s/echo-upstream.yaml`,
     `k8s/apisix-v316.yaml`, `k8s/apisix-v317.yaml`
   


-- 
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]

Reply via email to