[
https://issues.apache.org/jira/browse/HTTPCLIENT-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Klambauer updated HTTPCLIENT-2378:
-----------------------------------------
Description:
Hi! We have a problem similar/same as HTTPCLIENT-2093.
it seems not fixed with the other issue.
Basically, eg jetty responds early with an HTTP404 if a URL is not found,
while the HTTPclient is still sending the data if it has a big body, and the
server for 404 also closes the connection immediately.
the immediate connection close yields a broken pipe socketexception in the
execute httpclient method.
So depending on timing / http request body size, the result is either the
server status code (eg 404) or an exception.
best case would be to check for already returned http response when the
connection is closed (as the RFC reference in HTTPCLIENT-2093 mentions) - and
return normally from the execute method?
attaching a reproducer.
was:
Hi! We have a problem similar/same as HTTPCLIENT-2093.
it seems not fixed with the other issue.
Basically, eg jetty responds early with an HTTP404 is a URL is not found,
while the HTTPclient is still sending the data if it has a big body - as the
server for 404 also closes the connection immediately.
the immediate connection close yields a broken pipe socketexception in the
execute httpclient method.
So depending on timing / http request body size, the result is either the
server status code (eg 404).
best case would be to check for already returned http response when the
connection is closed (as the RFC reference in HTTPCLIENT-2093 mentions).
attaching a reproducer.
> Big request bodies and early server reponse yield SocketException instead of
> response
> -------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-2378
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2378
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (classic)
> Affects Versions: 5.5
> Reporter: Thomas Klambauer
> Priority: Minor
> Attachments: httpclient-bug.zip
>
>
> Hi! We have a problem similar/same as HTTPCLIENT-2093.
> it seems not fixed with the other issue.
> Basically, eg jetty responds early with an HTTP404 if a URL is not found,
> while the HTTPclient is still sending the data if it has a big body, and the
> server for 404 also closes the connection immediately.
> the immediate connection close yields a broken pipe socketexception in the
> execute httpclient method.
> So depending on timing / http request body size, the result is either the
> server status code (eg 404) or an exception.
> best case would be to check for already returned http response when the
> connection is closed (as the RFC reference in HTTPCLIENT-2093 mentions) - and
> return normally from the execute method?
> attaching a reproducer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
