[Bug 63337] New: mod_proxy_uwsgi returns 500 Internal Server Error on client read timeout

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug 63337] New: mod_proxy_uwsgi returns 500 Internal Server Error on client read timeout

Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=63337

            Bug ID: 63337
           Summary: mod_proxy_uwsgi returns 500 Internal Server Error on
                    client read timeout
           Product: Apache httpd-2
           Version: 2.4.39
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Other Modules
          Assignee: [hidden email]
          Reporter: [hidden email]
  Target Milestone: ---

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 '<a href="http://localhost:8080'">http://localhost:8080' -X POST -H 'Content-Length: 10'

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Bug 63337] mod_proxy_uwsgi returns 500 Internal Server Error on client read timeout

Bugzilla from bugzilla@apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=63337

--- Comment #1 from [hidden email] ---
Created attachment 36518
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=36518&action=edit
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.

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]