You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Vianney Carel (JIRA)" <ji...@apache.org> on 2010/08/19 22:28:17 UTC
[jira] Closed: (HTTPCLIENT-980) CachingHttpClient returns a 503
response when the backend HttpClient produces an IOException
[ https://issues.apache.org/jira/browse/HTTPCLIENT-980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vianney Carel closed HTTPCLIENT-980.
------------------------------------
Confirm it's fixed. Thanks :-)
> CachingHttpClient returns a 503 response when the backend HttpClient produces an IOException
> --------------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-980
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-980
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: Cache
> Affects Versions: 4.1 Alpha2
> Reporter: Vianney Carel
> Priority: Minor
> Fix For: 4.1 Alpha3
>
> Attachments: no-503-on-ioexception.patch
>
>
> The CachingHttpClient returns an HTTP 503 response when the backend HttpClient throws an IOException.
> It happens for instance when the backend is DefaultHttpClient (AbstractHttpClient), issuing a request to a server not listening on the target port.
> Well, it sounds tricky, but it makes the HttpClient not having a consistant behaviour in an implementation using both caching and regular clients.
> If a 503 should really be returned in that case, I suggest the AbstractHttpClient to return it and the CachingHttpClient to just propagate any exception thrown by the backend.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org