https://bz.apache.org/bugzilla/show_bug.cgi?id=59045
--- Comment #9 from Peter Pramberger <[email protected]> --- Unfortunately I can't do a real-life test with the application yet, this might take a couple of days, sorry. But when trying to manually test it, I noticed some strange behaviour (not related to your patch!): 1) Triggering a request header read timeout: $ openssl s_client -connect 10.15.24.4:443 -quiet <no input> <Connection closed after 20s, no output> [Mon Feb 29 13:21:26.240128 2016] [reqtimeout:info] [pid 1384:tid 140271576659712] [client 10.15.24.23:51325] AH01382: Request header read timeout 10.15.24.23 securities-backoffice-http-test.DOMAIN - [29/Feb/2016:13:21:26 +0100] "-" 408 - "-" "-" While a 408 is logged, there is no actual response from the web server. Shouldn't it return a "HTTP/1.1 408" status line? 2) Triggering a request body read timeout: $ openssl s_client -connect 10.15.24.23:443 -quiet POST /SecuritiesTool/rpc HTTP/1.1 Host: securities-backoffice-http-test.DOMAIN Content-Type: application/octet-stream Content-Length: 100 <no body sent> HTTP/1.1 400 Bad Request Date: Mon, 29 Feb 2016 12:21:33 GMT Server: Apache Content-Length: 318 Connection: close Content-Type: text/html; charset=iso-8859-1 [Mon Feb 29 13:21:54.466678 2016] [reqtimeout:info] [pid 1646:tid 140271608129280] [client 10.15.24.23:51327] AH01382: Request body read timeout 10.15.24.23 securities-backoffice-http-test.DOMAIN - [29/Feb/2016:13:21:33 +0100] "POST /SecuritiesTool/rpc HTTP/1.1" 400 318 "-" "-" What happened to the 408? -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
