https://bz.apache.org/bugzilla/show_bug.cgi?id=62249

            Bug ID: 62249
           Summary: Server only responding after timeout when there are
                    extra data after the request
           Product: Apache httpd-2
           Version: 2.4.33
          Hardware: Sun
                OS: SunOS
            Status: NEW
          Severity: regression
          Priority: P2
         Component: Core
          Assignee: bugs@httpd.apache.org
          Reporter: k.j.cher...@gmail.com
  Target Milestone: ---

Hi.

Looks like regression after 2.4.29.

I'm sending a request:
POST /path/to/app HTTP/1.1\r\n
Host: host:port\r\n
Content-Type: text/xml; charset=utf-8\r\n
Content-Length: 417\r\n
\r\n
<417_bytes_of_data>\s\r\n

In 2.4.29 I was always receiving a response:
HTTP/1.1 200 OK
Date: Mon, 02 Apr 2018 13:12:21 GMT
Server: Apache
Strict-Transport-Security: max-age=63072000; includeSubdomains; preload
Content-Type: text/xml;charset=utf-8
Content-Length: 1891

<1891_bytes_of_data>

In 2.4.33 sometimes I'm not receiving a response at all (until the connection
is being closed by apache after Timeout seconds), sometimes I'm receiving:
HTTP/1.1 200 OK
Date: Mon, 02 Apr 2018 13:08:23 GMT
Server: Apache
Strict-Transport-Security: max-age=63072000; includeSubdomains; preload
Content-Type: text/xml;charset=utf-8
Transfer-Encoding: chunked

and sometimes I'm receiving only part of response (and the rest of the response
is sent after Timeout seconds):
HTTP/1.1 200 OK
Date: Mon, 02 Apr 2018 13:14:08 GMT
Server: Apache
Strict-Transport-Security: max-age=63072000; includeSubdomains; preload
Content-Type: text/xml;charset=utf-8
Transfer-Encoding: chunked

544
<544_bytes_of_data>

However, in all cases the request made it to the application, but the client
did not receive a response.
Can you please tell me whether this Apache's behaviour is correct? If yes, is
there any RFC that can prove correctness of this behaviour (tried looking by
myself, but stuck at reading about HTTP pipelining -- according to it, this
request should be handled correctly).

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org

Reply via email to