[
https://issues.apache.org/jira/browse/HTTPCLIENT-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490304
]
Oleg Kalnichevski commented on HTTPCLIENT-648:
----------------------------------------------
A self-contained test case that does not require an external site to run would
be more preferable. Something along the lines:
http://svn.apache.org/repos/asf/jakarta/commons/proper/httpclient/trunk/src/test/org/apache/commons/httpclient/TestRedirects.java
You do not necessarily have to use SSL to reproduce the problem. You just have
to be able to re-create the condition of HttpMethodDirector overriding the
actual protocol socket factory with the default one.
Oleg
> A redirect does not use the same ProtocolSocketFactory as the original method
> -----------------------------------------------------------------------------
>
> Key: HTTPCLIENT-648
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-648
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient
> Affects Versions: 3.1 RC1
> Reporter: Thomas Mathis
> Fix For: 3.1 Final
>
> Attachments: TestBug_HTTPCLIENT_648.java
>
>
> I use a GetMethod with a special ProtocolSocketFactory and execute a
> GetMethod where followRedirects is true. The Server has a test certificate
> which is trusted in the used keystore.
> The primary GET is OK but the redirect does not use the same
> ProtocolSocketFactory and therefore fails because the server certificate is
> no longer trusted.
> I checked the code: the ProtocolSocketFactory is replaced at
> HttpMethodDirector line 617 -> HostConfiguration line 315.
> It is the same method as I stated in the bugreport HTTPCLIENT-646
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
