Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Medium
-
Resolution: Fixed
-
Affects Version/s: proxy:1.0.0
-
Fix Version/s: proxy:1.0.3
-
Component/s: proxy
-
Environment:any
-
Epic Link:
-
Frequency:Occasional - May occured/be used from time to time, in specific situation
-
Account:GZL25 - PROXY02.5 - Qualification - 580952 (580952)
Description
Relates to PROXY-518.
[ceoche 2024-12-12]
Faulty request is well recorded when the connection closes, but not the response.
I have made a test were the client send a request with a Content-Length too long to qualif2.ihe.kereval.cloud:10080, which is a channel that forward to interop.esante.gouv.fr:80. That server timeout the client (was also waiting for the end of the request) and respond with
HTTP/1.1 408 Request Timeout
Date: Thu, 12 Dec 2024 14:01:40 GMT
Server: Apache
Connection: close
Content-Type: text/html; charset=iso-8859-1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>408 Request Timeout</title>
</head><body>
<h1>Request Timeout</h1>
<p>Server timeout waiting for the HTTP request from the client.</p>
<p>Additionally, a 403 Forbidden
error was encountered while trying to use an ErrorDocument to handle the request.</p>
</body></html>
Unfortunatly the response is not recorded. Cannot reproduce with all channel, because many server timeout the client without sending response.
[ceoche 2024-12-12]
Faulty request is well recorded when the connection closes, but not the response.
I have made a test were the client send a request with a Content-Length too long to qualif2.ihe.kereval.cloud:10080, which is a channel that forward to interop.esante.gouv.fr:80. That server timeout the client (was also waiting for the end of the request) and respond with
HTTP/1.1 408 Request Timeout
Date: Thu, 12 Dec 2024 14:01:40 GMT
Server: Apache
Connection: close
Content-Type: text/html; charset=iso-8859-1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>408 Request Timeout</title>
</head><body>
<h1>Request Timeout</h1>
<p>Server timeout waiting for the HTTP request from the client.</p>
<p>Additionally, a 403 Forbidden
error was encountered while trying to use an ErrorDocument to handle the request.</p>
</body></html>
Unfortunatly the response is not recorded. Cannot reproduce with all channel, because many server timeout the client without sending response.
Attachments
Issue Links
- clones
-
-
- Closed
-