Re: [I] help request: a client request body is buffered to a temporary file [apisix]

["Baoyuantop (via GitHub)" <gi...@apache.org>]

Baoyuantop commented on issue #13367:
URL: https://github.com/apache/apisix/issues/13367#issuecomment-4622996648

   This warning is expected Nginx behavior, not necessarily an APISIX error.
   
   `PUT /apisix/admin/configs` sends the full declarative configuration to APISIX. When the request body is larger than Nginx's in-memory request body buffer, Nginx buffers the body to a temporary file and logs:
   
   `a client request body is buffered to a temporary file`
   
   This does not mean the request failed. In your access logs, the Admin API returned `202` and `204`:
   
   - `202` means the new configuration was accepted.
   - `204` means APISIX skipped the update because the digest/config was unchanged.
   
   Also note that `nginx_config.http.client_max_body_size: 0` only means APISIX does not limit the maximum request body size. It does not mean all request bodies are kept in memory. Whether the body is written to a temporary file is controlled by Nginx request body buffering, especially `client_body_buffer_size`.
   
   If you only want to reduce this warning for large Admin API config sync requests, you can increase the Admin API request body buffer size through the Nginx admin snippet, for example:
   
   ```yaml
   nginx_config:
     http_admin_configuration_snippet: |
       client_body_buffer_size 10m;
   ```


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org