Bug 63337 - mod_proxy_uwsgi returns 500 Internal Server Error on client read timeout
Summary: mod_proxy_uwsgi returns 500 Internal Server Error on client read timeout
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_proxy_uwsgi (show other bugs)
Version: 2.4.39
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: PatchAvailable
Depends on:
Blocks:
 
Reported: 2019-04-10 18:16 UTC by joshual
Modified: 2020-11-01 11:19 UTC (History)
0 users



Attachments
Return 408 Request Timeout on any timeout error reading HTTP request content from the client. (1.40 KB, patch)
2019-04-10 18:20 UTC, joshual
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description joshual 2019-04-10 18:16:58 UTC
Note: This was originally opened as in issue in the uwsgi project (https://github.com/unbit/uwsgi/issues/1677), but mod_proxy_uwsgi has been included as a 1st-party module in httpd, so I'm opening the issue here.

I believe the preferred result is an HTTP 408 Request Timeout response.

This can be easily reproduced using the following curl command, passing a content-length header without any content.

    curl -v 'http://localhost:8080' -X POST -H 'Content-Length: 10'
Comment 1 joshual 2019-04-10 18:20:55 UTC
Created attachment 36518 [details]
Return 408 Request Timeout on any timeout error reading HTTP request content from the client.

This patch was tested using the same curl command used to reproduce the original issue.